within_scope
The structured action satisfies the supplied permissions, limits, time window, resource boundaries, and configured gates.
Authorization intelligence for autonomous agents
Know whether the agent is actually authorized.
ScopeProof compares one proposed action with one explicit authority envelope immediately before execution. It returns a deterministic decision and a signed receipt without receiving raw prompts, credentials, or the target request body.
$0.01 per decisionExact-price stablecoin machine commerce
GlobalHTTP, MCP, payment, file, message, shell, generic
Signed Ed25519 receiptsEd25519 verification with public JWKS
No target executionScopeProof evaluates metadata only
Three explicit outcomes
A decision an enforcement point can actually use.
ScopeProof does one narrow thing: compare the proposed action to the supplied authority constraints and return a machine-readable result with reason codes.
review_required
The action reaches a configured approval or ambiguity boundary that the calling system should resolve before execution.
outside_scope
An explicit permission, deny rule, amount cap, resource boundary, timing rule, or other constraint failed.
The instant before execution
Authority in. Proposed action in. Signed decision out.
Keep authority checks separate from prompt interpretation and target execution. ScopeProof never needs to browse the destination or see the agent's underlying instructions.
1
Describe authority
Supply permissions, explicit denies, limits, timing, resource boundaries, and approval requirements.
2
Describe the action
Send only structured metadata for the exact action the agent proposes to perform.
3
Get the decision
Receive within_scope, review_required, or outside_scope with deterministic digests and reason codes.
4
Verify and enforce
Verify the signed receipt and apply your own accepted issuers and trust roots before execution.
Operations
Three endpoints, one narrow responsibility.
Free structural validation before payment, a one-cent substantive decision, and free cryptographic receipt verification afterward.
Preflight
Free
Validate schema, privacy boundaries, and secret-safety. Preflight intentionally returns no substantive authorization verdict.
scopeproof.preflightCheck action
$0.01 USD
Evaluate the exact action against the authority envelope and return the decision, reason codes, digests, and signed receipt.
scopeproof.check_actionVerify receipt
Free
Verify receipt signature, expiry, decision integrity, and deterministic digests using ScopeProof's public Ed25519 key set.
scopeproof.verify_receiptPrivacy boundary
Designed to keep secrets out of the decision path.
ScopeProof accepts the minimum structured information needed to evaluate authority and rejects secret-bearing material before any payment challenge.
What ScopeProof accepts
Bounded structured metadata that describes authority and the proposed action.
- Authority ID and validity window
- Allowed operations and resources
- Explicit deny rules and amount limits
- Destructive or irreversible action gates
- Optional caller-asserted approval reference
What ScopeProof does not need
Credentials and raw agent context stay outside the service.
- Raw prompts or arbitrary request bodies
- Passwords, API keys, cookies, bearer tokens
- Private keys or payment credentials
- Credential-bearing URLs or secret query strings
- Target fetches or target execution
Verifiable decision artifact
Carry the authorization decision forward.
Every paid ScopeProof decision can include a signed scopeproof-receipt.v1 so a downstream system can verify integrity without trusting a copied JSON field.
- Decision and explicit reason codes
- Action and authority digests
- Ruleset and evaluation digest
- Issued and expiry timestamps
- Public Ed25519 verification through JWKS
Receipt verification does not authenticate the authority issuer. Your enforcement point still decides which authority issuers and digests it trusts.
Machine-native by default
Discover, evaluate, pay, verify.
ScopeProof exposes HTTP and MCP discovery, stablecoin-first machine commerce, replay-resistant request binding, durable settled-result recovery, and public receipt verification surfaces.