Integrations
Build Pikeway into your product
Give your users, or your own agents, the whole Pikeway catalog. There are three ways to do it. They differ in who pays, who owns the user relationship, and how much you run yourself.
All three call the same gateway with a Pikeway key (pk-…), so discovery, per-call pricing and "only pay for successful calls" work the same way. The difference is whose key it is and what sits between your users and Pikeway.
Choose an approach
Direct
Your server, your key. Users never see Pikeway; you pay for every call.
Sign in with Pikeway
Users connect their own Pikeway account with OAuth 2.1 and pay from their own balance.
Your own proxy
Put your own auth, billing and allow-list in front of Pikeway, then forward approved calls.
Quick decision guide
- Building an internal agent, a backend feature, or a prototype, and happy to cover the cost? Use Direct.
- Building an agent app, MCP client or developer tool where each user should pay for their own usage? Use Sign in with Pikeway.
- Reselling API access inside your own SaaS, with your own prices, plans or credits, and a curated set of endpoints? Use Your own proxy.
Compare the approaches
| Direct | Sign in with Pikeway | Your own proxy | |
|---|---|---|---|
| Who pays Pikeway | You, from your balance | Each user, from their own balance | You; you bill your users however you like |
| Owns the user relationship | You. Users never see Pikeway | Shared. Users have a Pikeway account and approve your app | You. Users never see Pikeway |
| User needs a Pikeway account | No | Yes | No |
| Your own pricing | Bundle the cost into your product | No: users pay Pikeway list prices | Yes: markup, credits, plans |
| Spend controls | Per-key limits, agent keys, IP allowlist | User picks a limit at consent; revocable any time | Your own rules, plus key limits as a backstop |
| What you run | Nothing extra: call from your backend | An OAuth client and token storage | A proxy service you operate |
| Time to first call | Minutes | About an hour | A day or more |
You can combine them. A common setup is Direct for your own background jobs and Sign in with Pikeway for power users who'd rather spend their own balance. A proxy can also hand each tenant its own budget-limited key upstream.
What stays the same
- Same endpoints: the Agent API (
/v1/discover,/v1/inspect,/v1/run), the raw gateway (/gw/<slug>/…), the AI gateway and MCP. - Same billing: a fixed price per call, charged only on a 2xx upstream response, with
X-Pikeway-CostandX-Pikeway-Call-Idon every response. - Same key controls: spending limits, IP allowlists and site restrictions. See Keys, balance & billing.
Listing your own API instead?
These pages are about consuming the catalog. If you want your own API in the catalog so agents can find and pay for it, read the provider guide. Providers keep 90% of every call.