When an agent makes the introduction, who gets the referral fee?

Picture the owner of a 20-person IT services firm asking an AI assistant for three cybersecurity vendors that work well with MSPs. The assistant reads a dozen vendor sites, calls one vendor's pricing API, and pays a fraction of a cent for the privilege. It hands back a shortlist. Six months later, one of those vendors signs a $40,000 contract.

Who introduced that customer?

The agent paid for the API call. The vendor's logs show a signed request from a known AI operator. The payment cleared in seconds. And nobody has been credited, let alone paid, for the introduction.

That gap is the most interesting thing about the agentic web for a company like ours, which tracks referrals for a living.

The rails being built

In August, Cloudflare described the Agentic Internet it's building as "readable, discoverable, callable, and payable." In its September follow-up it added that "the last word, payable, is the one that determines whether the open web can fund itself." Several pieces of that are now real:

These are good pieces of infrastructure. Cloudflare says it sees more than 500 billion verified bot requests a week through Web Bot Auth. Monetization Gateway, in closed beta for U.S. sellers, lets a site charge agents per request, query, or token for pages, APIs, and MCP tools, using HTTP 402 and x402, with payments settled through Coinbase's facilitator in USDC on Base. Cloudflare's Pay Per Use pays publishers when verified AI buyers use their content.

Every one of them pays for access. A referral fee pays for origination. Those are different events, and no protocol on that list connects them.

Three kinds of value an agent can create

It helps to separate them:

1. Access. An agent reads a page or calls a tool. The resource owner can now charge for that, per call.
2. Influence. An assistant names you in a shortlist. That shapes the buyer's decision, but nobody agreed to anything. It's closer to word of mouth than to a referral.
3. Introduction. A specific party connects a specific prospect to a specific vendor, under an agreement about what happens if a deal closes.

The new rails handle the first one well. The second is what AI search visibility is about. The third is where referral fees live, and it still needs the same things it has always needed.

We've solved most of this before

Referral credit isn't a new problem. A finder's fee has long compensated someone for bringing two parties to a deal, on terms the paying party agreed to in advance.

Online, affiliate programs turned that into click tracking. Most pay the last click, which is easy to administer and often wrong about who created the opportunity.

B2B channel programs went another way. In deal registration, a partner registers a named opportunity, the vendor reviews it, and an approved registration protects that partner's claim to that deal.

The difference matters for agents. Click attribution asks which tracked touch gets the credit. Deal registration asks whether a named party has an acknowledged claim to a named opportunity. An agent-made introduction often produces no click at all. It needs something like registration.

Agents already write the shortlist

In G2's 2026 Buyer Behavior Report, more than 60% of B2B buyers said they use or plan to use AI agents in software buying. The top uses are all evaluation: comparing total cost of ownership (51%), building shortlists (51%), researching solutions (49%). Only 9% are comfortable letting an agent execute a purchase within approved guardrails, and 2% without pre-approval.

So agents shape vendor selection long before anyone trusts them to buy. The introduction happens earlier than any click, inside a conversation no vendor can see.

The assistant platforms aren't charging for those introductions either. OpenAI has moved away from standalone Instant Checkout and now sends buyers to complete purchases on merchant sites, and says, "There are no fees on purchases that start in ChatGPT." The companies writing the shortlists aren't taking a cut of the introductions. For now, that leaves the question with the businesses on both sides.

What referral credit still requires

When we say a referral "counts," we mean four things are true:

1. A registered introduction. A named prospect, a named introducer, a date, and the need that prompted it. Recorded when it happens, before anyone knows whether the deal will close.
2. An agreement. Who gets paid, how much, for what, and for how long. Agreed before the introduction happens.
3. Attribution that follows the deal. The introduction stays attached to the opportunity through every handoff until it closes or dies. That's where most referral programs quietly lose money.
4. A fee on collected revenue. Not on a click, a call, or a signed contract that never pays. Our product calculates commissions on collected invoices for this reason.

None of these need an agent to change. What changes is who the introducer is. An agent can't sign an agreement or receive a fee. The introducer is the person or business that directed the agent. If a fractional CFO has an assistant draft introductions to three vendors for a client, the CFO made those introductions. If a platform's assistant recommends you without any agreement, that's influence, and nobody is owed anything.

What to add to your referral agreements now

If you pay or receive referral fees, these terms are worth adding before agent-assisted introductions become routine. This is a starting point for a conversation with your lawyer, not legal advice.

1. Define an introduction. Include introductions drafted or sent by an agent on behalf of a party to the agreement. Exclude crawls, API calls, page visits, and general mentions in AI answers.
2. Require registration. The prospect, the introducer, any agent or tool used, the date, and the need. Give the vendor a set number of days to accept or reject, with reasons such as an existing account or a duplicate.
3. Require a human confirmation. The prospect or an authorized person confirms the introduction before it counts. That keeps an agent's shortlist from becoming a dozen competing claims.
4. Set an attribution window and a tail. How long after registration a deal still qualifies, and whether credit survives if the agreement ends.
5. Decide about multiple contributors in advance. Pre-existing opportunities, two registered introducers, an agent-assisted introduction followed by a human one. Exclusive, split, or not eligible.
6. Pay on collected revenue. Say how refunds, discounts, renewals, and expansions are treated.
7. Disclose paid relationships. The FTC's Endorsement Guides require disclosure when a connection "might materially affect the weight or credibility of the endorsement" and the audience wouldn't expect it. An agent recommending a vendor its operator is paid by is exactly that kind of connection.

Some industries have stricter rules. Lawyers generally can't pay for recommendations except in narrow cases, such as non-exclusive reciprocal referral agreements the client is told about. Mortgage settlement services fall under RESPA's anti-kickback rule. Routing an introduction through an agent doesn't change any of that.

An illustrative clause, again not legal advice:

An Agent-Assisted Introduction is a prospect-specific introduction made by Partner, or by an AI agent acting at Partner's direction, that is registered with Company, identifies the prospect, the agent or tool used, the date, and the business need, is confirmed by the prospect, and is accepted by Company. An automated request, content retrieval, page visit, or general recommendation alone is not an introduction.

Our referral fee agreement tool and attribution policy builder cover the rest of the basics.

The fair objections

"An agent mention is just another marketing touch." Often it is. Then treat it like one, and don't pay a referral fee for it. Decide in advance which is which.

"You can't prove the agent caused the deal." You can't prove most human referrals caused the deal either. That's why registration and agreed rules beat perfect measurement.

"Paying for recommendations will bias the agents." It's a real risk, and it's why disclosure matters. A paid introduction should be labeled, and it should never be passed off as a neutral ranking. We've written about why getting paid for introductions is fine when it's done in the open. The same holds when software does the introducing.

"Affiliate links already solve this." They do when there's a click. Agent introductions often have none.

So who gets the fee?

Whoever the agreement recognizes as having made a registered introduction. Not whoever paid for the API call, signed the request, hosted the assistant, or showed up last in a click log.

The agentic web is getting good rails for identity, access, and payment. Introductions, attribution, and commissions still need an agreement and a record that follows the deal. That's the layer we build. Kai, our AI partner manager, already handles intake and follow-up with a person approving every action.

I'll be at Cloudflare Connect this week, including Wednesday's session on building an open agentic Internet that's "discoverable, callable, and payable." If you're working on the payable part, I'd like to talk about the part that comes after.

FAQ

Can an AI agent earn a referral fee?

Not by itself. An agent can't sign an agreement or receive payment. The person or business that directed the agent can earn a referral fee, if their agreement with the vendor counts agent-assisted introductions and the introduction was registered and confirmed.

Do x402 or Cloudflare's Monetization Gateway handle referral fees?

No. They let a site charge an agent for access to a page, API, or tool, per request. A referral fee is paid when an introduction becomes a customer who pays, often months later. That needs an agreement and attribution, not a per-request payment.

What should a referral agreement say about AI-assisted introductions?

Define what counts as an introduction, including ones drafted or sent by an agent, and what doesn't, such as crawls and general AI mentions. Require registration and a human confirmation, set an attribution window, decide how multiple contributors split credit, and pay on collected revenue.

Do disclosure rules apply when an agent recommends a vendor?

If the agent's operator has a paid relationship with the vendor that the buyer wouldn't expect, disclosure is the safe course, and the FTC's Endorsement Guides require it in many cases. Lawyers, mortgage providers, and other regulated professions have stricter limits on referral payments.

Stop reading about referrals. Start tracking them.

Free up to 5 referrals a month. Every feature included. No card to start.