Orthogonal: The Service Layer Between AI Agents and Paid APIs

Orthogonal gives AI agents one integration to find and pay for paid APIs, without a separate account or key for each provider. Its website sums it up as "Tools and live data for AI agents." Behind that line is a catalog of 60+ providers and 1,000+ API endpoints, one shared balance, and support for x402, an open standard that lets an API ask for payment inside the HTTP request itself. Massive's Search endpoint is in that catalog; Massive supplies the endpoint and Orthogonal lists it. We called it through Orthogonal's gateway to see what an agent actually gets back, and the response is below.

Key Takeaways

• Orthogonal lets an agent use "the same key and balance across providers," with 60+ providers and 1,000+ endpoints (Orthogonal).
• It supports x402, so an agent can pay per request without opening an account.
• Massive's Search endpoint is live on Orthogonal's x402 gateway. Later pages of the same search are charged at zero.
• Orthogonal raised a $4.3M seed led by Pantera Capital in June 2026 (PR Newswire, 2026).

What problem does Orthogonal solve?

An agent that needs a company's headcount, a page of search results, and a scraped product page usually needs an account, a key, and a billing setup with each provider, sometimes after a sales call. People can push through that once per vendor. An agent hits it every time a task needs a new data source, and it shouldn't have to fill in a signup form or wait on a contract.

Orthogonal's co-founder Bera Sogut described the gap in the company's funding announcement: "Discovery, orchestration, and payments are the three critical problems standing between today's agents and true autonomy" (PR Newswire, 2026). Orthogonal's answer is a single catalog. Per its website, one account gives access to all 60+ providers, grouped into categories:

How does an agent use Orthogonal?

Orthogonal describes a three-step flow written for the agent rather than the developer:

1. Find the right API by describing the task.
2. Check the details: the inputs and the price.
3. Make the call.

The agent uses one Orthogonal key and one balance for every provider in the catalog.

Developers connect in one of three ways, per Orthogonal's documentation: a unified REST API; an MCP server at mcp.orthogonal.com that works with Claude Desktop, Cursor, and other MCP clients; or a command-line tool. From a terminal, orth search "web scraping" searches the catalog. The site shows Claude Code, Codex, and Cursor among the agents it works with.

Billing is pay per request, with "no per-provider accounts to manage," per the docs. Developers add credits in dollars with a card. For agents that pay on their own, the site says: "Agents can also pay through x402, MPP, or Nanopayments."

What is x402, and why does it matter for agents?

HTTP has had a status code for payments since the 1990s: 402 Payment Required, still listed in today's HTTP standard as reserved for future use. x402 is an open standard that puts it to work. An API answers an unpaid request with a 402 and a machine-readable description of what the call costs and how to pay. The client pays and retries, and the response comes back. There's no signup form and no invoice.

That suits agents, which can't sit through a procurement review. It also changes the economics for API providers: a single request can be a sale. A data API no longer needs a sales team to reach its next customer if that customer is an agent with a wallet.

What we saw when we called Massive Search through Orthogonal

We sent an unpaid request to Massive's endpoint on Orthogonal's x402 gateway on October 2, 2026:

curl -i "https://x402.orthogonal.com/joinmassive/search"

It returned HTTP/1.1 402 Payment Required, with a base64-encoded Payment-Required header. Decoded, the header describes the endpoint: it retrieves Google results, or queues a search for later, with geotargeting by country, subdivision, and city, and returns structured SERP data.

Three details stood out. First, the quoted price in that response was 12,500 base units of USDC, which is $0.0125 for the call at the time we checked. Prices can change, so treat that as a snapshot. Second, the description sets out a pagination rule: save the requestId from the first call, pass it as parentRequestId on later pages of the same search, and those continuation calls "are charged 0." Changing the filters starts a new billable request. Third, the request schema in the header lists 18 parameters. Most match Massive's native API, including awaiting for lazy features ("ai, answers, ads"), and the gateway adds plain country, subdivision, and city fields for location.

For an agent, this means live, geotargeted Google results with no Massive account: it pays from its Orthogonal balance or an x402 wallet. For teams that want the full native API, including serps for up to 10 pages in one call, see the Search endpoint docs.

Who is behind Orthogonal?

Orthogonal was co-founded by Christian Pickett (CEO) and Bera Sogut, and is backed by Y Combinator. In June 2026 it announced a $4.3M seed round led by Pantera Capital, with participation from Y Combinator, Pioneer Fund, Decasonic, Blast, Outbound, Surreal, and strategic investors. Pickett framed the bet in the same announcement: "Soon, there will be more agents than people online" (PR Newswire, 2026).

Where Orthogonal fits in the agent stack

In our map of the LLM search stack, the layers describe what agents read and do: answer engines, search APIs, retrieval, live web access, and agentic action. Orthogonal works across them as the layer that connects an agent to those services and pays for them. It doesn't replace any one provider; it makes a catalog of them reachable with one key. That's a different job from building a better search API or browser, and one more sign that agents are becoming customers in their own right. For how agents reach the live web in the first place, see how to give AI agents live web access and what the agentic web is.

Orthogonal: the bottom line

• One key and one balance instead of dozens of vendor accounts.
• x402 turns a single API call into a complete purchase, a payment model an agent can handle without a human approving each purchase.
• Use the gateway for account-free, per-request calls; use the native API when you need up to 10 pages in one call.
• Payment layers like this make agents direct buyers of web data.

Sources

• Orthogonal, "Orthogonal: Your agent's gateway to every tool and data source"
• Orthogonal Docs, "What is Orthogonal?"
• PR Newswire, "Orthogonal Raises $4.3M Seed for AI Agent Service Discovery, Orchestration, and Payments Across the Internet", 2026
• Y Combinator, "Orthogonal"
• IETF, "RFC 9110: HTTP Semantics", 2022
• x402, "x402"
• Orthogonal x402 gateway, Massive Search listing at x402.orthogonal.com (402 response and decoded Payment-Required header)
• Massive Docs, "Search"