Developers / build once

Use one request shape across supported sources.

See how Zenith is designed to authenticate a customer, check access, route an approved request, and return a standardized result with source evidence and usage details.

Explore MCP Browse Sources

Authentication overview

Credentials identify; policy authorizes.

The customer plane uses server-verified identity and entitlement. Sanitized examples are never active credentials.

Server-only verification
Hash-only key storage
Revocable customer credentials

Envelope contract

Errors and provenance are product surfaces.

A useful response distinguishes terminal failure from partial evidence and carries the context needed to evaluate freshness and source.

Stable request IDs
Machine-readable error codes
Source and normalization context

Capacity

Call weights are explicit integers.

Rate and monthly call-balance decisions happen before provider routing. No automatic overages are part of the approved model.

Logical calls separated from physical attempts
Monthly reset disclosure
Zero upstream on denial

Zenith Lens / non-executing

Inspect a sanitized request schema.

Select a capability, parameters, and language. The preview uses placeholders and sends nothing.

Capability

Provider pathatg.seLIVE routes1Call weight1 call unit

operation_id: Visible after authenticated catalog authorization
input: Validated against the selected operation schema

curl -X POST "https://<fina1-origin>/api/v1/execute" \
  -H "Authorization: Bearer <fina1-api-key>" \
  -H "Idempotency-Key: <unique-request-key>" \
  -H "Content-Type: application/json" \
  --data '{  "operation_id": "<authorized-operation-id>",  "input": {}}'

No network request is sent from this public lens. The authenticated customer gateway performs identity, tenant, entitlement, source-policy, availability, rate, allowance, and schema checks before Zenith dispatch.

Public structures / sanitized

Success, error, and provenance remain distinct.

These structures explain the public contract without publishing private operations, credentials, or endpoints.

REQUEST ENVELOPE

{
  "request_id": "req_preview_01",
  "operation": "weather.point_forecast",
  "parameters": { "latitude": 40.7128 },
  "policy_version": "preview.v1"
}

ERROR ENVELOPE

{
  "request_id": "req_preview_01",
  "error": {
    "code": "SOURCE_REVIEW_REQUIRED",
    "retryable": false
  }
}

PROVENANCE

{
  "source": "sanitized-example",
  "request_time": "2026-08-02T07:00:00Z",
  "call_charge": 1,
  "stored": false
}

Resilient state contract

Calm in every condition.

Use one request shape across supported sources. retains truthful context, navigation, and a safe next action when live records are empty or unavailable.

EMPTY

No published records

Heading, explanation, and recovery path remain.

Reserved layout

Text status and stable geometry prevent surprise.

DEGRADED

Verified context first

Unavailable data is labeled with an alternate path.

ERROR

No false success

Plain language, stable navigation, and safe recovery.