APIAPI

Authentication, authority and idempotency

Authenticate explicitly, respect Workspace access and bind every paid replay to an idempotency key.

API / MCP maturity

The public documentation is shareable, but API and MCP capability availability is governed by the live product manifest and account access. Foundation or experimental operations are not stability promises.

Bearer authentication

Send the MYEQ API token in the Authorization header. An invalid explicit Bearer credential fails closed; MYEQ does not silently switch identity to an ambient browser session.

curl https://myeq.pro/api/v1/production/capabilities \
  -H "Authorization: Bearer $MYEQ_API_KEY"

Workspace access is part of authentication

A valid token does not bypass project tenancy. Project routes verify current Workspace membership and fail closed when tenant evidence cannot be resolved.

Authority classes

Read inspects. Plan proposes without spending. Mutate changes project state. Spend dispatches paid work. Approve records accountable acceptance. Admin changes credentials or policy. Confirmation belongs to the authority, not to UI decoration.

Paid execution requires idempotency

Use a stable Idempotency-Key for a logical paid attempt and explicit confirmation. Do not automatically retry paid or mutating operations after an ambiguous outcome.

curl -X POST https://myeq.pro/api/v1/production/plans/PLAN_ID/generate \
  -H "Authorization: Bearer $MYEQ_API_KEY" \
  -H "Idempotency-Key: production-123-attempt-1" \
  -H "Content-Type: application/json" \
  -d '{"confirm": true}'

Workspace · Project · Asset · Entity · Storyboard · Plan · JobGenerated ≠ Certified