MyApi API Documentation

The MyApi REST API is how agents and applications reach your connected services. Every call carries an Authorization bearer token and a workspace header, and every endpoint declares the scopes it requires, so an agent can only reach what you granted it.

The reference covers the service proxy - one consistent request shape for every connected provider - along with the endpoints for tokens, personas, memory and context, device approvals, notifications, skills and the audit log. Each entry lists the required scopes, the request and response shapes, and a working example you can paste into a terminal.

Agents that support Agent Signing Credentials authenticate with an Ed25519 key pair instead of a bearer token, so the secret never has to be handed to the agent process at all. The docs walk through enrolling a key, approving the device, and signing requests, plus rate limits, error codes, and the bootstrap flow a fresh agent follows on first run.