Context Ops Builder Pilot

Verify access without exposing your key

Store the credential as the server-side UTILITO_API_KEY environment variable. Never paste it into this website, a URL, client-side code, support email, chat, or source control.

HTTP verification

Before adding a credential to your own environment, the API playground can make one bounded credential-free first call and export the same request shape.

curl -X POST https://utilito.dev/api/run \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $UTILITO_API_KEY" \
  -d '{"tool_id":"json-repair","input":{"input":"{name: Ada,}"}}'

MCP configuration

Set UTILITO_API_KEY in the MCP client's server-side secret environment, then send Authorization: Bearer $UTILITO_API_KEY to https://utilito.dev/mcp. Never place the key in a URL or browser bundle.

Plans, quota, and failures

Free requests return the free plan. Allowed paid requests return the pilot plan with these quota headers:

x-utilito-quota-limit
x-utilito-quota-remaining
x-utilito-quota-reset

Forbidden, exhausted, revoked, and authorization-unavailable requests fail with typed errors.

PAID_AUTH_INVALID — The bearer credential is invalid or revoked.
PAID_SCOPE_FORBIDDEN — The key does not allow this route or tool.
PAID_QUOTA_EXCEEDED — The shared paid quota is exhausted for the period.
PAID_AUTH_UNAVAILABLE — Paid authorization is unavailable and fails closed.
PAID_QUOTA_UNAVAILABLE — Strong quota coordination is unavailable and fails closed.

Rotation, cancellation, and support

Rotation uses a short overlap window and preserves the shared quota. Cancel through Stripe or email [email protected]; do not include a credential or payload. No uptime SLA, unlimited use, storage, payload logging, or instant provisioning is included.