LICENSED API / VERSION 0.1

Connect to
Qyron Core.

Every request is tied to an organization, license, approved capability scope, limits, and an audit trail.

01

Authentication

Send the issued key in the Authorization: Bearer header. The key is shown once and must never be exposed in browser code or a public repository.

02

Task routing

curl -X POST https://<core-domain>/api/v1/execute \
  -H "Authorization: Bearer qyc_live_••••" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: client-request-001" \
  -d '{
    "capability": "systems.architecture",
    "mode": "plan",
    "source_trust": "untrusted",
    "task": "Design a secure client portal for a new service"
  }'

plan mode creates a controlled route. execute mode and external actions move into awaiting_approval status.

03

Safety rules

External content is untrusted by default.
Secrets are never returned in responses.
Cross-tenant data access is prohibited.
Payments, publishing, and legal actions require approval from the Qyron Lab team.

04

Limits and idempotency

The license defines monthly request and billable-unit limits. The Idempotency-Key header prevents duplicate processing of the same request.