Delegated authority management API for AI agents · veracta.net

Delegated authority management for AI agents.

Veracta checks authority, evidence, reliance and accountability before an AI agent acts — returning allow, escalate or block, with a full audit trail. Not runtime monitoring. Not post-hoc review. A pre-action decision layer.

  • Records sources, revisions and policy matches
  • Captures AI assumptions and confidence
  • Checks authority before execution
  • Creates an immutable audit trail

Before your AI acts, ask Veracta.

Example — AI-generated Bill of Materials

An AI agent generates a BoM from drawing v2.3, spec rev A and approved parts library v4. Veracta records every source, assumption and confidence score before release — and escalates when two items fall below the confidence threshold.

Source drawings usedDrawing revisionCustomer specification revisionApproved parts library versionAssumptions madeLow-confidence itemsFinal release decision
AI Agent
wants to act
Veracta
authority check
Allow
Escalate
Block
Audit Trail
every decision
The problem

AI agents are moving from advice to action.

AI agents can now send emails, update systems, approve work, access data and trigger workflows. But most businesses do not have a simple way to decide what those agents are allowed to do, when approval is required and who owns the outcome if something goes wrong.

Identity tells you who the agent is.
Access tells you what it can reach.
Veracta tells you what it is allowed to do right now.
The core idea

Pre-action authority, not runtime observation.

Veracta is not a monitoring, tracing or forensic tool that inspects what software did after the fact. It is a delegated authority management layer that decides — before an AI agent acts — whether the action falls inside human-approved authority. Low-risk admin can happen automatically and be logged. High-risk actions involving money, reputation, sensitive data or external commitments escalate for approval. Actions outside authority are blocked.

Evidence before action

Evidence before authority.

AI agents can produce work that sounds confident, but businesses need to know what evidence was used before that work becomes action. Veracta records the sources, assumptions, confidence, policies and approval route behind every AI action.

Trust breaks when AI sounds certain but cannot prove itself.

Source documentsSource revisionApproved / unapproved statusEvidence qualityAssumptions made by the AIConfidence scoreMissing informationUnverified claimsPolicy matchedApproval route
How it works

One API call between intent and action.

Every action flows through the same sequence: the agent asks, Veracta decides, the outcome is audited — all before a single side effect hits your systems.

01 · Request

Agent requests an action

The AI agent calls POST /v1/check-authority with the intended action, target, amount or scope, and any relevant context.

02 · Decide

Veracta evaluates delegated authority

Veracta matches the request against active policies, delegated scopes, revisions and reliance sources — then returns exactly one decision.

03 · Decision returned
ALLOW

Agent executes the action

Signed audit entry with policy match and reliance sources

ESCALATE

Action paused, routed to a named human owner

Audit entry captures the approver, context and response time

BLOCK

Action refused before it executes

Audit entry records the failing policy and reason for refusal

04 · Audited outcome

Outcome is recorded before the agent executes

Veracta writes an immutable audit entry — with a signed audit_id, the policy that fired, the reliance sources, and a human-readable reason — before the agent is told it may proceed. If the decision is BLOCK or ESCALATE, no side effect ever runs.

Decision state

Authority depends on context.

Veracta does not need to understand the whole live state of a business. It captures the relevant decision state around the specific action an AI agent wants to take.

Action typeTransaction valueRisk levelReversibilityConfidenceEvidence qualityExternal commitmentData sensitivityRecipient or supplier statusDomain permit listDomain deny listHuman ownerExisting policy
Authority doctrine

State-dependent, proportional, revocable and auditable.

Authority should not be a permanent label. It should expand or contract based on the action, context, risk and evidence available at the moment an AI agent tries to act.

Inside authority, supported by approved evidence, low risk and fully loggedAllow
Uncertain, uses incomplete evidence, contains assumptions, exceeds authority or requires human approvalEscalate
Uses unapproved sources, lacks required evidence, breaches policy or sits outside authorityBlock
Everything Audit trail
API demo

Add authority checks to your AI agent in one API call.

Request
POST /v1/check-authority

{
  "agent_id": "finance_agent_01",
  "organisation_slug": "veracta-demo",
  "action_type": "approve_invoice",
  "action_summary": "Approve invoice from ABC Supplies for £1,250",
  "value": 1250,
  "currency": "GBP",
  "risk_level": "medium",
  "confidence": 0.82,
  "reversibility": "medium",
  "external_commitment": true,
  "data_sensitivity": "low",
  "recipient_domain": "abc-supplies.co.uk",
  "domain_status": "approved",
  "human_owner": "mike@gamesterinc.com"
}
Response
ESCALATE
{
  "decision": "ESCALATE",
  "reason": "This action involves money, creates an external commitment and exceeds the approved automatic authority limit.",
  "next_step": "request_human_approval",
  "audit_id": "audit_123",
  "authority_status": "outside_automatic_authority"
}
Agent call example
import requests

decision = requests.post(
    "https://api.veracta.net/v1/check-authority",
    headers={
        "Authorization": "Bearer va_live_...",
        "Content-Type": "application/json",
    },
    json={
        "agent_id": "finance_agent_01",
        "organisation_slug": "veracta-demo",
        "action_type": "approve_invoice",
        "action_summary": "Approve invoice from ABC Supplies for £1,250",
        "value": 1250,
        "currency": "GBP",
        "risk_level": "medium",
        "confidence": 0.82,
        "reversibility": "medium",
        "external_commitment": True,
        "data_sensitivity": "low",
        "recipient_domain": "abc-supplies.co.uk",
        "domain_status": "approved",
        "human_owner": "mike@gamesterinc.com",
    },
).json()

print(decision["decision"])   # ALLOW, ESCALATE, or BLOCK
print(decision["reason"])
print(decision["audit_id"])   # immutable audit trail

if decision["decision"] == "ALLOW":
    approve_invoice()
elif decision["decision"] == "ESCALATE":
    request_human_approval(decision["next_step"])
else:
    log_blocked_action(decision["audit_id"])

Copy the snippet, swap in your API key, and run it. Veracta returns ALLOW, ESCALATE, or BLOCK before the agent acts — with an audit ID you can rely on.

Policy examples

See how action type and risk level map to a decision.

Pick an action and a risk level. Veracta returns one of ALLOW, ESCALATE, or BLOCK with the exact policy that fired and a readable audit reason.

Action type
Risk level
Veracta decision
block
{
  "decision": "BLOCK",
  "action": "payment.transfer",
  "risk": "high",
  "policy": "policy:high_stakes.high_risk",
  "audit_id": "aud_5eab127cbh",
  "reason": "payment.transfer at high risk is outside delegated authority. Blocked pending owner re-delegation with a scoped, time-bound approval."
}
Audit reason logged to aud_5eab127cbh. Every combination writes a record-of-reliance entry the owner can later inspect, revoke, or replay.
Use cases

Wherever AI agents take real actions.

AI finance agents
AI sales agents
AI support agents
AI admin agents
AI workflow automation
AI agents inside Slack, Teams, CRM and finance tools
Example — Bill of Materials

AI can create the BoM. Veracta decides whether it is trusted enough to release.

An AI agent generates a project-specific Bill of Materials from drawings and specifications. Before it is released, Veracta checks the evidence behind it.

Which drawings were used
Drawing revision
Specification revision
Approved parts library
Missing items
Assumptions
Confidence per item
Human approval route
Audit trail
Record of Reliance

Assume automation. Prove trust.

A record of what the AI relied on — before it acts.

Veracta records the evidence behind AI action before execution. It captures what data, documents, policies, revisions, assumptions and authority rules the AI relied on when proposing an action.

As AI agents move faster across systems, businesses need to prove what information was relied upon, where it came from, whether it was approved, what state it was in, and who authorised the action. Veracta creates a record of reliance for every AI authority check.

Record of Reliance fields

Source systemSource documentSource document revisionData captured atData state at decision timeApproved / unapproved source statusPolicy relied uponAuthority rule appliedAI assumptionsConfidence scoreEvidence qualityHuman ownerApproval decisionFinal outcomeAudit ID

Example — Bill of Materials

  • AI-generated BoM
  • Source drawings used
  • Drawing revision
  • Customer specification revision
  • Approved parts library version
  • Assumptions made
  • Low-confidence items
  • Exceptions raised
  • Human approval route
  • Final release decision

AI creates the work. Veracta proves whether it can be trusted, authorised and released.

Veracta vs runtime observation

Decide before the action. Don't just watch it afterwards.

Runtime observation and forensic monitoring products record what AI systems did so teams can detect anomalies, investigate incidents and improve safety after the fact. Veracta stops risky actions before they happen by checking delegated authority at the point of decision.

TimingAfter the agent actsBefore the agent acts
Question answeredWhat happened?Is this action allowed?
Default outcomeDetect, trace and investigateAllow, escalate or block
Evidence capturedLogs, traces and session replaysSources, revisions, policy matches and reliance
Value to the businessVisibility and forensicsControl and accountability

Veracta complements observability and monitoring tools. It adds the delegated authority layer they are not designed to provide.

Veracta vs veracta.io

Similar name. Different layer of the stack.

People land here searching for veracta.io, an AI runtime monitoring product. Veracta.net is a different company solving a different problem: delegated authority before the action, not observation after it.

veracta.io
Runtime AI monitoring
When it runs
After the AI acts
Question it answers
What did the model just do?
What it inspects
Prompts, outputs, traces, session replays
Outcome
Detect drift, evaluate quality, investigate incidents
Built for
ML / AI observability teams
  • Passive: reads what the model produced
  • Can't stop an action from happening
  • Answers post-hoc questions about behavior
Veracta (this site)
Pre-action authority API
When it runs
Before the AI acts
Question it answers
Is this specific action allowed right now?
What it inspects
Delegated scopes, policies, sources, revisions
Outcome
Return ALLOW, ESCALATE or BLOCK with a signed audit_id
Built for
Platform, security and agent-engineering teams
  • Active: authorizes or refuses the action itself
  • Blocks unsafe actions before they execute
  • Answers the accountability question up front

If you're looking for AI runtime monitoring, veracta.io is the right destination. If you need an API that decides whether an AI agent is authorized to act — and leaves a record of that decision — you're in the right place.

Differentiation

Not another chatbot. Not another compliance dashboard.

Veracta is an action authority layer. It does not replace IAM, security or governance platforms. It gives builders a simple API to check authority at the moment an AI agent tries to act.

IAM

Controls identity and access.

AI governance

Manages policies, compliance and evidence.

Veracta

Controls action authority before execution.

Who uses Veracta

Builders integrate. Businesses control.

Agent builders integrate Veracta, but businesses control the authority boundaries. Every escalation routes to a named human owner.

Agent Developer

The developer or agency building the AI agent. They integrate the Veracta API into their agent code.

Company / End Customer

The business using the AI agent. They own the authority rules, human approvals, policies and audit trail.

Human Approver

The named person inside the company who approves, rejects or requests changes when an AI action is escalated.

Pricing

Start free. Upgrade when your agents start acting.

Start free. Add authority checks to your agent in minutes. Upgrade when your agents start acting in real workflows.

Free

£0/month

For testing and early builders

Includes 1,000 authority checks/month

Get started

Starter

£29/month

For solo builders and small agents

Includes 10,000 authority checks/month

Get started

Growth

£99/month

For SMEs and active agent workflows

Includes 100,000 authority checks/month

Get started

Agency

£299/month

For agencies managing multiple client workspaces

Multiple client workspaces and higher usage

Get started

Enterprise

Custom

For larger companies needing SSO, compliance support, custom limits, data controls and support

SSO, compliance and data controls

Contact us

Company-owned account

The company owns the Veracta workspace and pays directly. Developers are invited as integrators.

Developer / agency account

The developer or agency pays for Veracta and includes it in their agent build or monthly support package.

Veracta checks authority, evidence, reliance and accountability before AI action.

For developers

Developers use Veracta to make their AI agents safer and easier to sell.

For companies

Companies use Veracta to control what AI agents are allowed to do before they act.

FAQ

Common questions.

What is Veracta?

Veracta is a delegated authority management API for AI agents. Before an agent sends money, updates a system, commits externally or triggers a real-world action, Veracta returns allow, escalate or block — with the evidence, policy and reliance behind the decision.

Authority before action vs runtime observation after the fact

Veracta decides whether an AI agent is allowed to act before the action runs. Runtime observation and forensic monitoring products watch what software did after the fact. Veracta does not monitor traffic, trace calls or provide post-hoc forensics. It returns a decision at the point of action, then records the decision and evidence for audit.

Who is Veracta for?

Agent developers and agencies integrate Veracta to make their AI agents safer and easier to sell. Companies use Veracta to control what AI agents are allowed to do and to keep a full audit trail of every authority decision.

How does it work?

Your agent sends a single API call describing the action it wants to take. Veracta evaluates the decision state — action type, value, risk, evidence, confidence, policy and human authority — then returns allow, escalate or block, plus an audit ID.

What does Veracta cover?

  • Authority limits and policy checks before an action
  • Allow / escalate / block decisions
  • Evidence, source revision and assumption capture
  • Confidence scoring and low-confidence escalation
  • Human approval routing and named ownership
  • Immutable audit trail of every authority decision
  • Integration into agent code via a single API call

What does Veracta not cover?

  • Real-time traffic monitoring or log streaming
  • Post-execution forensics or incident reconstruction
  • LLM prompt tracing or token-level observability
  • General model evaluation or benchmarking
  • Identity and access management (IAM) replacement
Early access

Building AI agents? Add authority before action.

Veracta v0.1 is the first live API. Join early access to add allow / escalate / block authority checks to your agents.

Before your AI acts, ask Veracta.