API Explorer

Given an approved request plan, how is work represented across an API or HTTP interaction? Request/response model only — the runtime performs no network activity. Approval-gated. Read-only.

Sessions

Endpoints

Requests

Approval barriers

Internal service readready

1 endpoint · 1 request · 1 internal / 0 external

GET

External REST read + paginatedready

1 endpoint · 2 request · 0 internal / 2 external

GET

Authenticated writes + deletewaiting_approval

1 endpoint · 3 request · 0 internal / 3 external

POSTPUTDELETE1 destructive3 approval

GraphQL query + mutationwaiting_approval

1 endpoint · 2 request · 0 internal / 2 external

GRAPHQL1 approval

Webhook + SSE + upload/downloadwaiting_approval

3 endpoint · 4 request · 0 internal / 4 external

WEBHOOKGETPOST2 approval

Creative provider request (deferred)waiting_approval

1 endpoint · 1 request · 0 internal / 1 external

POST1 approval

CreditVector internal service (declared)waiting_approval

1 endpoint · 2 request · 2 internal / 0 external

GETPOST1 approval

The Universal API/HTTP Runtime owns request semantics, response expectations, endpoints, methods, headers (safe/secret-by-name/generated), parameters, body descriptors, auth requirements, secret references by name, timeout/retry/idempotency intent, pagination, webhooks, GraphQL, and streaming — as metadata. It performs no network activity: no fetch, sockets, TLS, DNS, or SDK calls. Real dispatch is owned by the future Broker, gated on a binding Policy allow, with secrets injected by the future Vault.