Sponge

Sponge developer resources

Use this page to discover the existing Sponge agent surface. Sponge does not publish GraphQL, an MCP server, OAuth for third-party apps, webhooks, or a commerce API.

When to call Sponge

Bring your own inference to create or revise one private document. Delegate a bounded research job when Sponge's research agent adds value. Read an exact released Entity, Inquiry, or Edition without a token. Hand review, rights, identity, editions, and publication back to a person.

Do not call Sponge as a generic model API, as a public write surface without a person-issued token, or as a way to publish automatically.

Discovery

• Agent manifest
• OpenAPI 3.1
• OpenAPI 3.1 alias
• RFC 9727 API catalog
• Sponge research skill
• Programmatic research in product docs
• Machine-readable site guide

HTTP contract

Private calls use a short-lived bearer token created by a signed-in person on the Agent access page. Every operation publishes its exact scope, document-boundary rule, and byte limits in OpenAPI. Canonical reads return a bare Sponge-Revision. Semantic writes require Sponge-If-Revision and a fresh idempotency key. Errors are JSON objects with error.code, error.message, optional error.requiredAction, and meta.requestId.

Anonymous public reads are limited to exact released artifacts at /api/v1/public/artifacts/{kind}/{artifactId}/{revision}. Unknown /api/v1 paths return JSON NOT_FOUND.