Substy Build with Substy
Connect your agency’s workflows, data, and tools through one API.
The Substy API gives your applications access to the same guarded operations used by our AI agent integration. Work with creators, conversations, analytics, campaigns, content, and your team using ordinary HTTPS requests.
Production access
Use the API at api.substy.ai. Access is enabled per agency and respects the issuing user's current permissions.
Get API access
Check agency availability and create a personal key with the permissions you need.
Make your first request
Authenticate, find your agency, and list its creators.
Explore the API reference
Request fields, responses, and code examples generated from the server’s full endpoint catalog.
Choose precise permissions
Grant a key the categories it needs, within your own agency role.
Handle limits and retries
Build reliable integrations with the shared agency request budget.
Connect your AI agent
Set up Substy in Claude, Claude Code, Codex, or Cursor with browser sign-in.
Documentation for agents
A plain-text index, Markdown pages, and the full OpenAPI specification.
What you can build
Read performance and revenue, organize fan records, manage media and publishing, schedule campaigns, launch scripts, configure AI behavior, and coordinate your team. Every request respects the key’s agency, category grants, and the issuing user’s current role and creator access.
Direct conversational replies to fans are unavailable through this integration. Scheduled messages, bulk campaigns, scripts, and AI controls are available within their granted categories. Creator login cookies, platform tokens, and other connection secrets are excluded from responses.
One platform, two interfaces
Use the REST API for software integrations and MCP for assistants such as Claude. They share permissions, business rules, and rate limits. You do not need to translate a REST request into an MCP tool call.
The downloadable specification is available from the API at /openapi.json. This reference is generated from the same source during the documentation build.