API reference

Build against a clear, governed API surface.

Browse the public endpoints intended for applications, agents, and protected resources. Filter by workflow and authentication boundary, then move into a quickstart or SDK when you are ready to integrate.

Authorize your first action Use an SDK

26 public endpoints
20 bearer-guarded
Tenant-bound authorization model

Integration workbench

Find the endpoint. Understand the boundary. Integrate safely.

This reference is read-only. It helps teams inspect the public surface without connecting the marketing site to a 2AYE environment.

26 endpointsArrow keys move through the list

GETRuntime authorization

/v1/evaluations/{id:guid}

Read a resource or collection without changing authority.

Authorization boundaryTenant-bound bearer token

Send an access token for the tenant addressed by the request. Cross-tenant authority is refused.

Request

curl -X GET "<your-2aye-api>/v1/evaluations/{id:guid}" \
  -H "Authorization: Bearer <access-token>" \
  -H "Content-Type: application/json"

Common integration handlingSchemas are in the published specification

2xx — request accepted
401 — token missing or invalid
403 — tenant or authority refused
409 — state or parameter conflict

This page documents the public integration surface only. Administrative and operational routes are intentionally excluded. Confirm request and response schemas in the published specification before production integration.

The enforcement path

Follow every endpoint above from identity to evidence.

Each consequential action moves through the same six control points. See where 2AYE evaluates authority, requests human review, and preserves the outcome.

01IdentityWho or what is acting
02IntentSigned purpose and limits
03PolicyDeterministic evaluation
04ApprovalA named human when required
05ExecutionSingle-use grant, redeemed at the resource
06EvidenceReceipt joined to the audit chain

Build against a clear, governed API surface.

Bring the next consequential action under control.