Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

Orthogonal

One integration for agents to discover and pay for APIs

Details

External ID
49523765
Source
HN
Company
—
Product
Orthogonal
Website domain
orthogonal.com
Launched
Sept. 1, 2026
Cohort
—
Upvotes
12
Upvotes percentile
0.6419457735247209
Tags
—
Fetched at
Sept. 10, 2026, 5:31 a.m.
Updated at
Sept. 10, 2026, 5:31 a.m.

Description

Hey HN, we're Bera and Christian, and we're building Orthogonal.Orthogonal gives AI agents one integration to discover, access, and pay for APIs. Think OpenRouter for the APIs that AI agents use.We currently have 50+ API providers and 700+ API endpoints across company, people, financial, and web data, available through our MCP server and SDK on a pay-as-you-go basis. We started with GTM related APIs and are now expanding the catalog.You can try at https://www.orthogonal.com/. You'll need to create an account to use the chat or connect the MCP/SDK.An example prompt for the chat or MCP: Find AI infrastructure startups that recently raised a Seed or Series A and return their founders, LinkedIn profiles, and relevant company data.When we heard about https://x402.org/, we saw an opportunity to make APIs easier for agents to pay for. Instead of an agent needing to manage an API key and billing for every API, what if it could just pay for each request?So we started onboarding existing API providers onto x402. Then we realized an agent cannot pay for an API it doesn’t know exists. It also needs to figure out which API can complete the task and how to use it.We also found that putting every small API payment on-chain did not always make sense. If both sides already have accounts with Orthogonal, settling internally is simpler. So we separated API discovery and access from the payment rail.Today, payments can happen through Orthogonal credits, x402, https://mpp.dev/, or https://www.circle.com/nanopayments.The problem we're working on now is API selection.If five APIs can answer the same request, which should the agent use? The cheapest might have worse coverage. Another might be more accurate but slower.We're working on using price, latency, reliability, and result quality to help agents make those decisions.How are you currently giving agents access to paid APIs?And if you gave an agent a budget, would you trust it to choose which API provider to spend it on?

Enrichment

Theme
AI agent frameworks and developer tools
Vertical
Horizontal
Function
Agent / copilot
Audience
Developer
AI stance
AI feature
Project type
Commercial product
Normalized one-liner
api discovery and payment integration for agents
Manually corrected
False

Could you build this?

Partial The proxy gateway and unified SDK are vibe-codeable, but negotiating billing, reselling 50+ third-party APIs, and handling unified metering and settlement require non-trivial infrastructure and business operations.

What it would actually take: The technical architecture involves an API gateway (e.g., Envoy or Cloudflare Workers) that normalizes input schemas, routes to 50+ provider upstream endpoints, and meters usage per call. The system needs a low-latency ledger/wallet service supporting micropayments, credit debiting, and third-party rate limiting/error fallback handling. The hard part is the complex commercial integrations, billing reconciliation, and maintaining unified schemas across rapidly changing upstream SaaS APIs.

Discussion

No comments on this launch.

Competitors

Other products that read as similar to this one — 239 launches clear the similarity bar, closest 8 shown.

Attention rank: #106 of 240 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 305 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a agent / copilot tool for Agriculture yet.