2AYE
Guides, reference & supportCapability status
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.

This is a curated public integration catalog. It excludes administrative and operational routes, including parts of account, subscription and credential management. The endpoint count is not the platform's full route inventory. Confirm application permissions, tenant access and product eligibility for the operation you intend to use.

  • 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 skeleton / supply endpoint-specific fields
# Bash: Request skeleton: supply endpoint-specific fields before sending.
curl -X GET "<your-2aye-api>/v1/evaluations/{id:guid}" \
  -H "Authorization: Bearer <access-token>"
Common integration handlingSchemas are in the published specification
  • 2xx — HTTP request processed; inspect the outcome
  • 401 — token missing or invalid
  • 403 — tenant or authority refused
  • 409 — state or parameter conflict

HTTP success is not action authorization. Runtime evaluations may return DENY or require approval in a successful response. Inspect the decision, follow the required approval ceremony, and present a valid exact-action grant to the configured execution boundary. Never execute solely because the HTTP status is 2xx.

Examples use synthetic identifiers. Replace them with resources in your tenant and a currently signed intent; refresh requestedAt before submitting an evaluation. For other routes, define the request body from the endpoint contract before copying the skeleton.

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.

  1. 01IdentityWho or what is acting
  2. 02IntentSigned purpose and limits
  3. 03PolicyDeterministic evaluation
  4. 04ApprovalA named human when required
  5. 05ExecutionSingle-use grant, redeemed at the resource
  6. 06EvidenceReceipt joined to the audit chain
Deterministic decisionsSingle-use, exact-action grantsHash-linked evidence