Skip to main content
This page is for companies that want AI agents to recommend their service. The Gravity Index is a recommendation API for AI agents and platforms. Coding agents in Cursor, Claude Desktop, and Claude Code use it, and so do custom agents and chat products. When an agent recommends your service, the user gets the reasons and a tracked link to your signup page.

Why list your service in the Gravity Index

Distribution through agents

Agents call gravity_index_search through the Gravity Index MCP server. Your service can show when a developer asks an agent for “a database” or “payments for Next.js”.

Recommended in context

Platforms can share a conversation summary with the Index. The Index then recommends you when the user has the problem that you solve, not only when a keyword matches.

CPA: pay only for results

There is no CPC and no CPM. You set a cost per acquisition (CPA). You pay only after a confirmed conversion or a completed integration.

How it works

1

You get listed

Send Gravity your service details (slug, name, category, description, tags) and the URL of your signup page. Gravity reviews the details and adds the service to the catalog.
2

An agent finds you

An agent calls gravity_index_search with a request, for example “managed Postgres with branching”. The Index can recommend you and give the reasons.
3

The user clicks

The response has the reasons, a click_url, and a grclid (Gravity click ID). The link sends the user to your signup page with the click IDs in the URL, and records attribution. A click alone does not create a conversion or a CPA charge.
4

You get a signup, and Gravity gets the CPA

The user signs up on your platform. You confirm the signup through your conversion feed. If your listing has a CPA, the confirmed conversion creates the CPA charge.

Click IDs on your signup page

When a user opens a click_url, Gravity redirects them to the landing page of your listing and adds the click IDs as query parameters. These are the same parameters as on an ad click: grclid, grcpid, grpuid, gradid, and grsig. Index clicks do not have graid. See Click IDs on the landing page for what each one means.
  • Gravity replaces any gr* parameters that are already in your URL, and it leaves out parameters that have no value.
  • If your listing comes from a CPA campaign, the landing page is the landing page URL of the campaign, with the UTM parameters that you set on the campaign.
  • If your tracking system needs the click ID in a parameter with a different name, put the {grclid} macro in the landing page URL or in a UTM value, for example https://yoursite.com/signup?subid={grclid}. Gravity replaces the macro with the click ID. Gravity also adds the grclid parameter.
Store grclid when the user arrives, and send it with the conversion.

Costs

Each listing has a default_cpa_cents value. This is the amount that Gravity charges for each confirmed conversion. A publisher can turn on a private setting that gives a small boost to services with an active CPA campaign. Relevance stays first. The output that agents see never shows prices or payouts.

Improve your listing

After Gravity lists your service, three things have the most effect:
  1. A short, clear description: one or two sentences on what you do and who it is for. The Index reads it to decide if you fit the user’s problem.
  2. The correct category and tags: they decide the searches for which you are a candidate.
  3. A signup page that matches the description: the user comes from a recommendation that told them why you fit. The page must confirm that fast.

Machine-payable checkout (MPP)

An agent can buy your product directly if you accept payments through the Machine Payments Protocol with a Stripe Shared Payment Token. Give Gravity your payment link, and the Index returns it with your listing. The agent pays you directly with a one-time Link credential (link-cli mpp pay). Gravity is never in the payment path.

What to send

For each listing, send one value: How you add the link depends on how Gravity listed your product. Your listing comes from a CPA campaign (the usual case): the campaign builder has no payment link field. Send the payment link to Gravity (see Get listed), and Gravity adds it to the listing. Your listing is an older Index listing: your sidebar shows an Index item. You can add the link yourself:
  1. Open your advertiser dashboard.
  2. In the sidebar, click Index.
  3. Click the row of the product.
  4. Open Let AI agents pay for this product.
  5. Paste the URL into Payment link for agents.
  6. Save.
The sidebar shows Index only when your account has an older listing that is not linked to a campaign. When you save, Gravity gets the link one time. It reads your Stripe profile_ network ID from the 402 challenge (method="stripe", methodDetails.networkId), so you do not type it. If the link does not return 402 at that time, Gravity still stores it. Then network_id is null, and agents read the ID from your challenge when they pay. The price stays on your side. The agent reads it from the challenge, so you can change it at any time. The product must be yours. Gravity rejects a link for a listing that a different advertiser manages. Stripe does not create an MPP endpoint for each Stripe Product or Price. You create a route on your own server. Protect it with mppx and your Stripe account. Then paste the URL of the deployed route into the dashboard.
  1. Turn on machine payments for your Stripe account. Copy your Business Network profile ID (profile_) from Account > Profile.
  2. Run npm install mppx stripe. Then put one endpoint for each plan behind mppx:
  3. Deploy the route. Its URL (for example https://api.acme.dev/mpp/pro-plan) is your payment link.
  4. Test the link:
    The response is 402, with a WWW-Authenticate: Payment header that contains method="stripe".
If you already sell over MPP, send Gravity the URL that you give to other agents.

What agents get

When the recommended listing has a payment link, POST /search returns it like this (shortened):
If your URL has a {grclid} macro, Gravity puts the click ID there. Gravity also always adds grclid as a query parameter. Listings without a payment link return checkout: null and the usual click_url.

Confirm the conversion

An MPP purchase does not go through the click_url redirect. The grclid in the query string of your endpoint connects the sale to the recommendation. When the charge is successful, send it to Gravity from your server as a CAPI Purchase event, with user_data.grclid set to that value. Use CAPI for these sales, not the Stripe connector. The connector reads checkout.session.completed and invoice.paid. An MPP charge is a PaymentIntent that comes from the Shared Payment Token, and the connector does not read it. For your own reconciliation, you can also copy grclid into the metadata of the PaymentIntent.
Do not send Gravity Shared Payment Tokens, Link credentials, or Stripe secret keys. Gravity does not accept them.

Badge

Gravity gives you an “Available via Gravity Index” badge for your docs. A link back to Gravity is optional.

Get listed

Send an email to index@trygravity.ai.