What Onboarding 700+ x402-Enabled API Endpoints Are Teaching Us About Agent Commerce

x402 made agent payments possible. We have worked on what sits on top of it: discovery, pricing, and fulfillment. Our partners at Coinbase see the same thing:

"The promise of x402 isn't simply that agents can make payments. It's that they can discover, economically reason, and pay for the right service at the moment they need it. Orthogonal is putting that idea into production across 700+ endpoints and 50+ providers, showing how an open payment standard can turn the API economy into something agents can navigate autonomously."

Kevin Leffew, AI Partnerships, Coinbase Developer Platform

We believe millions of autonomous agents will soon research, build, book, and buy on behalf of consumers and businesses. To operate independently, these agents need to discover the right service, understand its price, obtain authorization, pay, and verify that the service delivered.

Orthogonal now makes more than 700 API endpoints from over 50 providers available to agents through x402. The most active workflows are already practical: GTM teams enriching contacts, investors monitoring company signals, and agencies building prospect lists for clients.

Why x402?

Model Context Protocol arrived about a year before x402 and got people giving agents tools. Later, when we discovered x402, we understood that crypto and micropayments were a clear fit for machine-to-machine transactions at the volume and speed agents will operate at.

x402 gave us the rails, but for a while the other half of the equation was still missing: agents that can transact. That changed around January 2026, with Claude Code and OpenClaw making agents more capable so they could stand up and control their own wallets.

However, there was not an easy way to set up x402 at the time without managing your own wallet and x402 endpoints. We believed an easy path would be needed, along with a company driving adoption forward and attracting non-crypto companies. Coinbase was doing a great job attracting initial companies and we wanted to help accelerate that.

What We Built on Top of x402

As we began onboarding API providers, partners consistently asked for additional application-layer capabilities around fulfillment, pricing, and discovery. We built these services above the x402 payment layer:

Refunds. Facilitators did not have support for managing refunds, so each API that implemented v1 had to manage its own refund policy. We decided to refund if an endpoint did not fulfill the request.

Request-based dynamic pricing. When a request came in, we parsed what was in it and set the price based on the fields present. That flexibility was not native to x402 v1, but came later in v2.

Discoverability. Bazaar provided a shared discovery surface for x402 services. We built natural-language search and request-time routing across our catalog, taking factors such as task fit, availability, and price into account.

We Have Brought More Than 50 New Providers onto x402

Through Orthogonal, agents can now access more than 50 API providers using x402, including Massive, RocketReach, Olostep, Tomba, Scrape Creators, and Apollo. Together, they span company and people data, search, scraping, phone and email services, virtual machines, and browser automation.

Use Cases in the Wild

We are seeing real agent transactions, real endpoint requests, and real usage across the payment rail, now spanning over 700 API endpoints. The usage patterns tell their own story: the heaviest activity so far comes from GTM teams enriching contacts, investors surfacing signals for deal sourcing and diligence, and marketing and recruiting agencies running similar plays for their clients.

Contact Enrichment

Contact enrichment is one of the most common requests we see through Orthogonal. Say you tell your agent:

I have a list of 50 leads with just names and company names. Get me their verified work emails.

The agent does not need to know in advance which provider can answer that. It queries Orthogonal's catalog of 55+ API providers spanning contact enrichment, company data, search, and more, gets matched to the right endpoint for the job, and receives pricing back. It pays, and the result comes back in the same flow.

Most used API providers for contact enrichment:

1. ContactOut, for finding personal emails and phone numbers from LinkedIn profiles
2. Fiber AI, for verified contact data
3. Tomba, for email finding and verification

Investor Signals

One customer put an agent below the CRM to watch signals across their portfolio and draft outreach personalized to each company's moment. Instead of integrating and maintaining a growing list of data providers, the agent queries Orthogonal's catalog and gets matched to the right source for each signal, all in the same flow.

The result: in the first two weeks, 87% of the company updates surfaced were independently grounded, up from near zero before Orthogonal.

Most used API providers for surfacing investor signals:

1. Coresignal, for company, employee, and job data
2. Aviato, for funding, investment, and founder data
3. Bytemine, for funding and acquisition signal tracking

Finding Leads

Sometimes the task is not enrichment, it is discovery. One customer uses Orthogonal as one of their sources for finding people to invite to events: pulling in candidates who match a given profile, not just filling in data on contacts they already have.

That is a search problem before it is an enrichment problem, and it usually means an agent needs different kinds of sources: company and people databases, web search, and sometimes a scrape. Rather than integrating each of those separately, the agent queries Orthogonal, gets matched across search and people-data providers, pays for what it uses, and comes back with a working list, ready to be handed to the same flow as contact enrichment.

Most used API providers for finding leads:

1. Apollo, for people and company prospecting
2. Company Enrich, for company data for prospecting
3. Nyne.ai, for contact and profile intelligence

What's Next

Discoverability and orchestration are where we are focused near term, along with governance and spend controls, limits, self-service API onboarding, and a control plane so companies can manage agent capabilities with confidence.

If you are looking for a curated set of x402-enabled APIs your agents can use, come try Orthogonal: https://orthogonal.link/Rx5M47D.