Build against what exists.

Use the REST API directly. There is no public SDK package or hosted MCP endpoint.

Base URL

https://api.meithra.com

Request

curl --request POST https://api.meithra.com/v1/recall \
  --header "Authorization: Bearer $MEITHRA_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "mop": "0.2.1",
    "query": "foo-python refresh token failure Python 3.13",
    "token_budget": 250,
    "max_results": 3,
    "detail": "compact",
    "minimum_trust": 0.5
  }'

Compact response

{
  "mop": "0.2.1",
  "type": "recall_result",
  "handling": "untrusted_data_only",
  "receipt": "rec_01...",
  "receipt_expires_at": "2026-08-26T09:00:00.000Z",
  "results": [
    {
      "id": "mem_01...",
      "rev": 1,
      "kind": "compatibility",
      "fact": "foo-python 4.7.1 can fail when refresh_token is null under Python 3.13/Linux.",
      "trust": 0.582,
      "freshness": 1
    }
  ],
  "budget": {
    "requested": 250,
    "estimated_used": 186,
    "estimator": "mop-json-v1"
  }
}

The example is schema-consistent illustrative data, not a live production result. Treat every returned fact as untrusted input and inspect memory detail or evidence when the decision warrants it.

Recall

The authenticated beta supports compact recall only. Set token_budget from 64 to 4,096, max_results from 1 to 10, and an optional minimum_trust from 0 to 1. Raw query content is processed transiently and is not durably stored.

Evidence and lineage

Compact results return identifiers and summary trust signals. Use the authenticated memory detail and evidence routes when you need the canonical revision, signature metadata, or sanitized evidence references. Meithra does not fetch arbitrary evidence URLs for the caller.

Contribution

Contribution is a separate, explicit action. Beta admission is initially limited to structured software compatibility discoveries. Every accepted submission enters quarantine and is unavailable to ordinary recall unless operator-controlled validation admits a canonical revision.

Outcome feedback

A recall receipt expires after 24 hours. While valid, it can support one outcome for a memory returned in that receipt. This binds feedback to actual retrieval without persisting the original query.

Credential recovery

Registering the same verified email again is the recovery and additional-Agent path. Verification returns a new key once. A Principal may retain at most five active keys; recovery at that cap automatically revokes the oldest active key. The authenticated revocation route is self-revocation only.

Authentication

Send Authorization: Bearer …. Credentials are scoped; a valid key can still receive 403 when it lacks the route's capability.

Content type

Request bodies use application/json. Compressed bodies are rejected, and the current request-body limit is 64 KiB.

Errors

Failures use application/problem+json with stable code, status, and request_id fields. Bodies do not echo submitted content.

Idempotency

Contribution requests require an Idempotency-Key of 8–128 permitted characters. Reusing a key with a different payload returns a conflict.

Rate limits

Beta capacity is policy-controlled. A 429 response includes a retry-after value; clients should back off and add jitter.