Get an API key for your user
start_signupStarts getting a free API key. Say what data your user wants and what they want to do with it; ask them if you do not know, and do not guess. Returns a link for your user to approve in the browser. Show them the link and code, then call finish_signup.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"data_wanted": "<data_wanted>",
"use_case": "<use_case>"
},
"name": "start_signup"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent | No | Your agent or client name. | |
| details | No | Any other fields worth telling us, with any names you like, for example language, schedule or team_size. Up to 20. | |
| found_us | No | Optional. How your user says they found this API, in their words, for example a web search or a recommendation. Ask once. If they do not say, leave it out: never guess or fill in a placeholder. Up to 300 characters. | |
| use_case | Yes | What they want to do with it. 3 to 1000 characters. | |
| data_wanted | Yes | What data they are looking for: leagues, stats, tiers, history, refresh speed. 3 to 1000 characters. | |
| agent_found_us | No | Optional. How you, the agent, found this API. Kept apart from found_us. Up to 300 characters. |