Agent-ready by default
Everything the rinkats portals do, your own tools and agents can do too — over a versioned REST API, a Model Context Protocol (MCP) server, and an A2A endpoint. One access model across all three: a credential carries exactly its user's access, never more.
What's here
- MCP — packaged, task-level tools an agent calls once to get a decision-ready result.
- A2A — the same capability surface for agent-to-agent flows (preview).
- REST —
/api/v1, zod-validated, strict HTTP status codes, an OpenAPI 3.1 document at /api/v1/openapi.json.
Three steps to your first call
- Create a key on your account page and scope it to the roles you need.
- Send it as
Authorization: Bearer rk_p_…. - Try any endpoint live from the reference — the try-it console sends the real request.
Where to go next
Authentication
One access model everywhere: a credential carries exactly its user's access, never more.
API keys
Self-serve, user-scoped keys — create, list and revoke on your account page.
Errors
Strict HTTP status codes and a consistent error body across every endpoint.
MCP
Packaged, task-level tools an agent calls once to get a decision-ready result.
A2A
The same capability surface over JSON-RPC for agent-to-agent flows.
Agent skills
A packaged SKILL.md an agent can install to work rinkats from inside its own tools.
Reference
Every REST endpoint, generated from the OpenAPI 3.1 document, with a live try-it console.