Skip to main content
Goro is a pay-per-call gateway. Your agent connects once, and gets a catalog of tools that reach the real world: search, social profiles and posts, maps and reviews, product and jobs data, image and video generation, and voice in both directions. You hold one balance and each call draws from it. A plan fills it every month with more credit than the plan costs, and once you are on one you can add credit as you go too. A scrape bills the published rate for what it actually consumed; an image or a voice call bills a price you can read before you make it.

​
Why it exists

Every one of these tools already exists somewhere, behind its own account, its own key and its own bill. Wiring five of them into an agent means five signups, five credentials and five invoices before it makes a single request. Goro is one credential and one balance for all of them.

​
How a call works

1

Discover

Ask what can answer your question. discover ranks the catalog against a plain-English query and returns each option with its price.
2

Inspect

Read the exact input a tool expects, plus a sample you can fill in.
3

Run

Make the call. Goro holds an estimate against your balance, runs the tool, then charges what it actually cost and releases the rest.
Discover and inspect are free and need no plan. Run needs an active plan: without one it answers 402 subscription_required instead of running. See Pricing.

​
Two surfaces, one catalog

Goro speaks HTTP and MCP, over the same catalog, the same balance and the same prices. The MCP server exposes six tools (discover_tools, inspect_tool, create_upload, run_tool, get_run, wallet_balance), each a thin wrapper over the same code the HTTP endpoints call.

​
What Goro keeps, and for how long

Goro records what a call cost, how many rows it returned and when it ran. That part is permanent. The rows themselves are held only until you collect them. A finished run keeps its results so a slow job stays collectable, then they are deleted shortly after your first fetch, and in all cases 24 hours after the run finished. The window is deliberately the shortest one that makes a paid run reliably deliverable: this catalog can reach personal data about people who have no relationship with us. Capture what you need when you get it. It has a consequence worth planning for. A run’s rows can stop being available even though its status and cost stay readable forever, so keep the rows from the response that hands them to you. The same goes double for media: a voice call answers with a link to audio that expires on that same 24 hour clock, and an image call answers with links held by the model provider. Download the file, do not save the URL.

​
Start here

For AI agents: Skill

Teach an agent the API in one file, no client library.

For AI agents: MCP

Add Goro to Claude, Cursor or any MCP client as a connector.

For applications: OAuth

Let your product connect on a user’s behalf, with their balance.

For humans

Get a key, make a call, watch the balance move.