Bring your own connector
Keep execution in your systems.
Make authority explicit.
Companies can integrate an existing application or automation with the 2AYE authority model. Evaluate the reference contracts first, then agree a scoped integration and protected-resource acceptance.
Five adapter responsibilities
These are responsibilities to implement in your existing adapter, rather than a new issuer or a second policy engine.
- 01
Describe
Declare the adapter owner, version, tool, allowed actions, input schema, credential scopes and protected destination. A catalog entry is not an approved connector.
- 02
Validate
Normalize and validate the exact target and material arguments. Use registered predicates; keep free text, prompts and provider payloads outside the closed predicate envelope. Bind external content through the documented content mechanism.
- 03
Authorize
Authenticate in the correct tenant and call the canonical evaluator against a signed intent. Stop on denial or pending review. An HTTP success or a decision object is insufficient authority to execute.
- 04
Execute
Require a valid grant for the exact tenant, agent, intent version, destination and parameters. The destination must enforce single use and current admission. Keep reusable provider credentials out of agent/model context.
- 05
Receipt
Observe the actual effect, return the required verifiable evidence, and correlate it with the decision and grant. On a lost response, reconcile destination state before another write.
Use the existing API surface
- POST /v1/runtime/evaluations
- Canonical evaluation of the registered predicate envelope. No parallel authorization-decisions endpoint is introduced.
- GET /v1/runtime/authorizations/{id}
- Retrieve the issued grant under authenticated tenant scope.
- POST /v1/runtime/authorizations/{id}/consume
- Reference redemption flow. External protected resources must follow the published destination-redemption contract and their registered trust boundary.
- POST /v1/runtime/authorizations/{id}/receipt
- Reference execution receipt flow. A reported success must be assessed against authentic destination effect evidence.
Prove refusals alongside a real effect
Test changed resources and parameters, another tenant, expired or revoked authority, concurrent redemption, provider failure and lost acknowledgments. Preserve an unrelated positive control. Verify artifact signatures and key identity independently. Independent validation and production availability require their own evidence.