Autonomy needs
more than access.
It needs authority.

Control which actions an agent can take, set clear limits,
and bring people in when approval is needed.

Try an authorization workflow.

Change the amount, adjust a limit, or review an approval.
See how each choice changes the result.

VERAUTHOR workspaceProduct demo

Change a request, review its authority, then approve or reject it. Every control below works with sample data.

Decisions

Sample data · this browser only

Customer refund

Principal
Refund agent
Resource
Example payment 001

Automatic limit: £100.00. Change it in Authority.

ALLOW

Within delegated authority.

The requested amount is within the example grant. You can simulate release without contacting a payment system.

Synthetic data only. No live authorization, payment or deployment. An authorization decision is not proof of a completed action.

Human oversight where policy requires it.Inside the platform

A clear boundary.
Not another
black box.

Put explicit authority between an agent’s request and the system that can act on it.

Explore the enforcement model

Your workflow.
A stronger boundary.

Keep your agent and your upstream system. Integrate authority at the point where an action becomes consequential.

Python SDKTypeScript SDKMapped HTTPMCP reference
Read the integration guide

Bounded adapter contracts—not drop-in vendor integrations. MCP deployment acceptance remains separate.

Fit authority into your workflow.

  1. Identify the request

    Define the agent, action and resource.

  2. Apply the boundary

    Evaluate the request against its delegated limits.

  3. Keep the decision

    Retain authorization evidence for review.

Developer documentation

Designed for control.
Clear about scope.

Explicit authority. Tenant-bound control. Signed decision evidence. Human step-up approval.

And an equally explicit distinction between tested software, a validated pilot and production acceptance.

Security & readiness

Know what
you’re trusting.

Is VERAUTHOR an identity provider?

No. VERAUTHOR evaluates authority for an exact action. The mapped HTTP interface authenticates configured workload credentials; it does not replace your identity provider or imply OIDC, SSO or mTLS integration.

What does ALLOW / HOLD / DENY mean?

ALLOW permits an unchanged request under the applicable authority. HOLD stops it for the configured human approval process. DENY blocks release. Real protection also depends on restricting direct access to the upstream.

Does a signed receipt prove the action succeeded?

No. A decision receipt verifies the recorded authorization decision and its integrity. It is not proof that a downstream refund or deployment completed.

How can my team evaluate the product?

Start with a scoped pilot: one workflow, reviewed adapter contracts, named approvers, test identities and an isolated or staging target. Agree success criteria before production expansion.

Discuss your workflow.

Define the actions, limits and approval process your team needs.

Let’s discuss your pilot