Skip to content

Noemad Docs

Application and inference API

Familiar inference contracts with explicit wallet and payment extensions.

Runtime v1.2. The public API shares this origin. Only qualified routes from /calculate/models are enabled. The current live model is amanai/gpt-6-luna for Chat Completions.

Endpoint directory

Public surfaces

SurfaceContract
/v1/chat/completions, /v1/responses, /v1/messagesProduct key or supported playground session; qualified reference JSON/SSE
/v1/models and /v1/usageQualified catalog and owner-scoped usage
Files, jobs and modality routesOriginal resource contract with product ownership checks
/_monad/v1/auth/challenge and /_monad/v1/auth/verifyWallet challenge and verification
GET /_monad/v1/operations/{id}Owner-only inference and collection status

Payment headers

RUNTIME HEADER CONTRACT
PAYMENT-REQUIRED
PAYMENT-SIGNATURE
PAYMENT-RESPONSE
Idempotency-Key
X-Monad-Operation-Id

The Idempotency-Key binds a credential, route and request body to one operation. A payment-aware client preserves the exact key and body when submitting authorization. Generic clients do not automatically understand this extension. Final payment status may arrive after streaming, through the owner-only receipt endpoint.

Request example

example
POST /v1/chat/completions
Authorization: Bearer <product-api-key>
Content-Type: application/json
Idempotency-Key: <unique-request-key>
PAYMENT-SIGNATURE: <bounded-authorization>

{
  "model": "<qualified-model>",
  "messages": [
    {
      "role": "user",
      "content": "Summarize this brief."
    }
  ],
  "max_completion_tokens": 512,
  "stream": true
}

Ownership and retries

One chain/token/payer/nonce/spender tuple binds to one operation. Scope idempotency to owner, route and canonical body. Repeated proof reads existing state rather than dispatching a second request. Shared provider accounts never expose another wallet’s resources.

Compatibility directory