HTTP JSON / OpenAPI 3.1

A small API.
An honest contract.

Discover stored sources. Inspect their metadata. Continue your task. Null means unknown, and database failures are never empty results.

OpenAPI specification ↗Agent manifest ↗Manifest Agent prompt ↗

Interactive explorer

Try the contract before connecting your agent.

REQUESTS GO TO THIS INSTANCE

Make a request

Public queries need no token. Query examples explicitly use discovery:off to read stored memory without starting work. Opting into discovery:on_miss may start budgeted background web discovery, persist unreviewed observations, and use provider quota; do not send secrets. Editorial routes are documented below but intentionally have no browser token entry.

Endpoint Request JSON

Known scope conflicts exclude a record. Missing metadata is included as unknown unless unknown_policy is exclude. No shipping or product availability filters exist.

Ready. No request sent.

Inspect the response

Your structured response will appear here.

Selected operation: request schema or parameters

Loading OpenAPI schema…

All response and nested schemas

Loading…

Endpoints & editorial workflow

JSON bodies: maximum 256 KiB. Search: 1–20 literal terms, up to 50 results, 1,000 candidates with explicit truncation. Unreviewed metadata is labeled; stale/rejected records are excluded. Editorial access requires a private bearer token; if unset, private inspection and all mutations are disabled. Protected GET can retrieve inactive records for re-review; public GET cannot. Imports are create-only and atomic. PUT replaces a complete source document using expected_revision, returning 409 for stale edits.

Errors: 400 malformed JSON · 401 unauthorized · 403 editorial disabled · 404 not found · 409 conflict · 413 too large · 415 wrong content type · 422 invalid contract · 503 database unavailable. See OpenAPI for the structured error schema. The manifest is descriptive, not a native connector installation promise.

Ingestion is explicit

Run schema setup, then import reviewed JSON through the protected CLI workflow. Starting the app never seeds or overwrites records. Optional background discovery adds unreviewed observations on public query misses.

Editing is conditional

Inspect a source, export editable fields, change the JSON, and PUT it with its current revision. Concurrent changes are rejected, not silently lost.

Integration is honest

Any authorized HTTP client can use this contract. Native ChatGPT and specific Muse integrations require separate verification.