Skip to main content
If your agent can make HTTP requests and read instructions, it does not need a Goro SDK. It needs a key and a page of rules. This is the right path for a coding agent, a background worker, or anything running in a loop you control. If you are wiring up Claude, Cursor or another MCP client, use the MCP quickstart instead.

1. Get a key

Create a workspace at app.usegoro.ai and generate an API key. New workspaces start with a small promotional balance, so the agent can make real calls before you add a card. Put it where your agent keeps secrets, conventionally as GORO_API_KEY.

2. Give the agent the rules

The full instruction file is published at usegoro.ai/SKILL.md. Point your agent at that URL, or save a copy as a skill file, a system prompt, or whatever your framework calls its instruction file. Prefer the hosted copy where you can. It is generated against the live API and covers the parts an agent gets wrong on its own: that result counts apply per target, that a scrape’s quoted price is a ceiling while an image or voice price is exact, that a media link expires, and that it should reach for your own tools before spending the balance. The short version below is the same contract, condensed.

3. Watch it work

The first call an agent makes should be discover. If it goes straight to run with a slug it guessed, the instructions did not land.
Every run shows up in the dashboard’s usage view with its cost, and in GET /v1/wallet/activities as ledger entries.

Full API reference

Every endpoint, field and error code.