BaseCite developer resources
Build server-side BaseCite integrations for tenant-scoped uploads, canonical processing status, persistent-storage quota, verified webhook events, and complete withdrawal of originals and derived context.
Start here
- Agent index
- Authentication
- Pricing and quota
- Developer guide
- BaseCite OpenAPI contract
- BaseCite MCP metadata
- BaseCite MCP server card
- Smithery MCP registry listing
- Official MCP Registry listing
- Public agent discovery repository
- Agent Plugin manifest source
- Portable MCP configuration
- BaseCite agent skill
- BaseCite MCP adapter on npm
Integration boundary
Credentials remain server-side. Every organization-scoped request names one organization and one upload where applicable. Clients must use idempotency keys, verify SHA-256 completion, poll canonical status for asynchronous processing, and never infer completion from a timer.