StoryTerranSoulMemory graphTry itTesseresServicesPricingMy AppsAccount overviewValuesDownloadContact
ENVI

Developers

Terranimus, as an API.

Each Terranimus product is getting a documented API with keys and quotas, and the same abilities as MCP tools for AI clients. This page lists the ones you can call now and the ones being built, with what each one needs from you.

Providers

What you can call.

  • Memo

    Live

    Memory and retrieval over your own documents: search, context for a prompt, answers with citations, and a document store you write to. AI clients reach the same memory as MCP tools.

    For
    Developers and businesses building assistants, and every Terranimus app.
    Auth
    REST: a memo_ key as a Bearer token (or X-API-Key), limited to the scopes on the key. MCP: OAuth 2.1 sign-in as yourself, or the same key.
    Key format
    memo_<region>_…
    Scopes
    readwriteingestsharedanswerusagememo:memory

    Answer and chat call a language model, so they draw on prepaid credit.

    Request access

  • Marketing MCP

    Live

    The Terranimus Marketing workspace as MCP tools: plan and draft content, work leads and prepare bookings from ChatGPT, Claude or any MCP client, acting as the person who signed in.

    For
    Client businesses that run their marketing workspace from an AI assistant.
    Auth
    OAuth 2.1 with PKCE, as the signed-in workspace member. Scopes go read, then write, then approve. Publishing, sending and anything else that reaches the outside world waits for the person to confirm in the web app.
    Scopes
    marketing:readmarketing:writemarketing:approve

    Switched on after its independent security review passed.

    Request access

  • Recruit MCP

    Live

    The Terranimus Recruit workspace as MCP tools: jobs sorted into direct employers and recruitment agencies, the likely client behind an agency ad, prospects and agencies, acting as the person who signed in.

    For
    Recruiters and sales teams who want to reach the employer behind a job ad.
    Auth
    OAuth 2.1 with PKCE, as the signed-in workspace member. Scopes go read, then write, then approve. Confirming a client, removing data or changing members waits for the person to confirm in the web app.
    Scopes
    recruit:readrecruit:writerecruit:approve

    Switched on after its independent security review passed. Job ad text is written by strangers and comes back marked untrusted.

    Request access

  • Identity

    Live

    Sign-in and access for apps: OpenID Connect, and an API for the signed-in person, their organisations and memberships, access checks and app registration.

    For
    Terranimus apps, and client businesses that want their own apps to sign in with Terranimus.
    Auth
    OpenID Connect. API calls carry a JWT access token issued for the Identity API (ask for it with resource=). An ID token is never an API credential.

    Identity becomes the one issuer of keys, plans and usage records for every other provider.

    Request access

Plans

The plans every provider is moving to.

One set of tiers for every product, once keys are issued centrally. Until then each provider applies its own limits, described with its API. Limits count per key or per sign-in grant, never per IP address. A call over a limit gets 429 with Retry-After, and the body names the window it hit.

PlansPer minutePer month
Free601,000
Dev60050,000
Pro3,0001,000,000
EnterpriseBy contract
  • Prices in AUD and VND are set for each product when it launches.
  • Endpoints that call a language model run on prepaid credit only.
  • Only enterprise carries an SLA, and only for a product that runs on two servers.

The contract

What every provider is moving to.

  • Versioned paths (/v1). A breaking change ships as /v2 beside it, with at least six months’ notice.
  • Keys named for the product and the environment (live or test), shown once, stored only as a hash, and revocable.
  • An OpenAPI 3.1 document for every REST API, and MCP tools that call the same functions, so the two cannot drift apart.
  • One error shape, and a request id on every response.
  • Anything that reaches the outside world, such as sending, publishing or charging, waits for a person to confirm in the app.
  • Text a third party wrote comes back in a field marked untrusted, never mixed into instructions.

Access

Ask for a key.

Keys are issued by hand for now, while self-serve keys are built. Write to us with the product, what you are building and the plan you expect to need.

Request access

For AI agents

The same list, as plain text.

Every provider with its addresses and how it authenticates, in the llms.txt style, for agents and scripts.

/developers/llms.txt