# Your agent already knows how to use Skysay
URL: /blog/works-with-any-ai

The MCP + llms-full.txt thesis — why an agent-native telephony API needs no bespoke integration.

Most APIs assume a human will read the docs and write an integration. An agent-native API assumes the opposite: the agent reads the surface and calls it directly. Skysay is built for the second world.

## MCP is the integration

Every Skysay capability is an **MCP tool** with a declared `required_scopes` contract. An agent points its MCP client at `POST /mcp`, passes a scoped `sky_` key as a Bearer token, and the tools appear in `tools/list` — coverage search, agent wiring, call evidence, SMS, policy-gated outbound. There is no SDK to install per language, no glue code to maintain. The [MCP overview](/docs/mcp) has the shape; the [tool reference](/docs/tool-reference) has every tool and its scope.

## llms-full.txt is the manual

Point an agent at [`/llms-full.txt`](/llms-full.txt) and it pulls the entire docs and blog corpus in one request — every page's processed markdown, cross-linked to the API's own `/control-plane/openapi.json` and `/control-plane/llms.txt`. Every page is also available as raw markdown by appending `.md` to its URL, so an agent can fetch exactly the page it needs without scraping HTML.

## Fail-closed keeps it safe

"Works with any AI" does not mean "does anything". The scoped key is the permission boundary: a `tools/call` for a tool whose scopes are not on the key fails closed with `missing MCP scopes`, every call is pinned to the key's organization, and live outbound is policy-gated. An agent gets exactly the capabilities it was granted — and nothing else.

## Try it

The [Quickstart](/docs/quickstart) covers installing the connector, minting a key, and inspecting your workspace. To hear your configured agent, use a [browser test](/docs/trial-calls).

> [!NOTE] August 2026 update
>
> Shared-number live PIN trials are retired. Browser tests use welcome credit or purchased funds; real phone calls require purchased funds and a configured route. See [Billing and browser credit](/docs/billing).