> ## Documentation Index
> Fetch the complete documentation index at: https://docs.signa.so/llms.txt
> Use this file to discover all available pages before exploring further.

# AI onboarding

> Point AI tools and coding agents at the Signa API

Signa's docs and API are built to be read by AI agents, not just people. This page is the map: what to point an agent at, and when to use each option.

## The docs themselves

Every page ships a plain-Markdown version alongside the rendered HTML. Use the menu in the top right of any page to copy it as Markdown, or open it directly in Claude, ChatGPT, Cursor, or VS Code.

For a single file covering the whole site, point an agent at:

```
https://docs.signa.so/llms.txt
```

`llms.txt` lists every guide and API reference page with a one-line description, so an agent can decide what to fetch instead of crawling the site.

## The OpenAPI spec

For codegen, request validation, or building your own tool definitions, the machine-readable spec is:

```
https://api.signa.so/v1/openapi.json
```

It covers every endpoint, parameter, and response shape in the [API reference](/api-reference/introduction). Feed the URL to an OpenAPI-aware codegen tool, or hand it to an agent that can fetch and reason over JSON schemas directly.

## The hosted MCP server

If your AI tool speaks [MCP](https://modelcontextprotocol.io) (Claude, ChatGPT, Cursor, and most agent IDEs do), Signa runs a hosted MCP server at `https://api.signa.so/mcp`. Connect it and an agent can search, retrieve, and monitor trademarks conversationally, no client code required. See [MCP server](/ai/mcp) to connect, and [Tools & permissions](/ai/mcp-tools) for the full tool list and scopes.

## The agent skill

For coding agents, install the `signa` skill in the project you're building in:

```bash theme={null}
npx skills add signa-so/skills
```

It packages the API conventions an agent otherwise guesses wrong (auth, filters, the watch DSL, pagination, error handling) so generated integration code is correct on the first try. See [Agent skill](/ai/skill).

## The TypeScript SDK

When an agent is writing code against Signa rather than calling it directly (a script, a backend integration, a scheduled job), point it at the `@signa-so/sdk` package. It's typed end to end, so an agent gets autocomplete and compile-time checks instead of guessing field names from example JSON. See [TypeScript SDK](/sdk/typescript).

## Which one to use

* **Exploring the API or drafting a prompt**: give the agent the docs or `llms.txt`.
* **Generating a client or tool definitions**: use the OpenAPI spec.
* **Letting an agent act on your Signa account conversationally**: connect the MCP server.
* **Having a coding agent build your integration**: install the [agent skill](/ai/skill).
* **Writing a script or service that calls Signa**: use the TypeScript SDK.