Build with AI - Securitize Developers

Coding agents such as Claude Code, Cursor and Codex can read everything on this site. Connect them once and they work from the current docs, for every Securitize API documented here.

Docs MCP server

The recommended way in. The MCP server lets your agent search the docs and read any page or API description file, so it answers from the current contract instead of from memory. It is read-only and needs no credentials: it reads the documentation, never your data.

claude mcp add --transport http securitize-docs https://developers.securitize.io/mcp

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "securitize-docs": { "url": "https://developers.securitize.io/mcp" }
  }
}

codex mcp add securitize-docs --url https://developers.securitize.io/mcp

Add this URL as a remote (streamable HTTP) MCP server:
https://developers.securitize.io/mcp

llms.txt and Markdown pages

For tools that read files rather than connect to a server:

What	Where
Index of every page	`/llms.txt`
The full text in one file	`/llms-full.txt`
Any page as Markdown	Add `.md` to its URL

Each Markdown page starts with short rules for agents, such as which base URL to use and the mistakes to avoid.

Add it to your repository

Paste the lines for the API you integrate into your repository’s AGENTS.md (or CLAUDE.md), so your agent knows where to look:

## Securitize SecId API
- Docs for agents: <this site>/llms.txt (append `.md` to any page URL for Markdown)
- Sandbox only unless told otherwise; the OAuth client id and secret are in the env vars SECID_CLIENT_ID and SECID_CLIENT_SECRET. Never print them or the token.
- Read the guide for your investor type ("Onboard an individual" or "Onboard a company") and "Errors" before writing integration code.

## Securitize CET Underlying API
- Docs for agents: <this site>/llms.txt (append `.md` to any page URL for Markdown)
- Sandbox only unless told otherwise; the Ed25519 signing key is in the env var CET_SIGNING_KEY. Never print or log it.
- Read "Sandbox and authentication", the buy or sell guide, and "Errors" before writing integration code.

## Securitize Stocks API (Beta)
- Docs for agents: <this site>/llms.txt (append `.md` to any page URL for Markdown)
- Beta: paths and fields can change. Sandbox only; the API key is in the env var STOCKS_API_KEY. Never print it, and never call the API from frontend code.
- Read "Prepare an investor to trade", "Trade a stock" and "Errors" before writing integration code.

## Securitize Corporate Actions API (Beta)
- Docs for agents: <this site>/llms.txt (append `.md` to any page URL for Markdown)
- Beta: paths, fields and event names can change. Sandbox only; the client id and secret are in the env vars CA_CLIENT_ID and CA_CLIENT_SECRET, the webhook signing secret in CA_WEBHOOK_SECRET. Never print or log them, and never call the API from frontend code.
- Read "Sandbox and authentication", "Receive webhooks" and "Errors" before writing integration code.

Agent skill

/skill.md summarizes the APIs in the Agent Skills format, and /.well-known/skills/index.json lists it for tools that discover skills on their own.

From any page

The Copy page menu at the top of every page copies it as Markdown, opens it in Claude or ChatGPT, connects the MCP server to Cursor or VS Code, or downloads the API’s description file.

Keys and agents

Give your agent sandbox credentials only, in environment variables. Never paste a key, a secret or a token into a prompt; the docs tools above never ask for one.