Developers

Use Tune.Toys from scripts, publisher automation and agents: API keys, limits, webhooks, embeds, MCP and schemas.

Status: The developer platform is implemented locally. Third-party OAuth, a hosted MCP endpoint, paid usage packs and CORS for browser-side keys are planned. Rate-limit numbers are proposed defaults pending an owner decision.

The API is described by an OpenAPI 3.1 document generated from the same route declarations the server runs. Use the route index here, or the interactive Swagger UI on tune.toys, which can send requests with your key. Download openapi.json for code generation.

I want toGo to
Make my first callQuickstart
Understand keys and scopesAuthentication
Know how fast I can callRate limits
Handle failuresErrors
Page through listsPagination
Retry writes safelyIdempotency
React to eventsWebhooks
Put a Toy on my siteEmbed API
Drive Tune.Toys from an agentMCP server and agent documents
Use TypeScriptSDK
Validate a ToyJSON Schemas

Edit this page on GitHub · Updated 2026-11-01

esc

↑ ↓ move↩ open⌘↩ new tabesc close