AI AGENTS Sandbox available

Agent autonomy.
Human control.

Let agents do the work. Keep the important decisions in human hands. Soliton verifies a real person’s presence, captures their consent and ties that permission to the action.

Physics-based verification. Action-bound permission. A record your business can validate.

THE HUMAN BEHIND THE ACTIONConcept
Agent requestsA specific action
Person approvesInformed consent
Business validatesPermission to proceed

VERIFIED BY SOLITON

A real person.
Behind this permission.

Live presence, grounded in physics.
Consent tied to the action.

Presence + consent
The agent continues. The proof stays.What was approved, who approved it, and what happened next.

Your policy decides when a person steps in.

ProceedRequest approvalStop

THE MOMENT PERMISSION MATTERS

From the agent’s request
to a person’s permission.

Your business sets the boundary. Soliton connects the agent, the person and the evidence at the moment permission matters.

MuseGrok Bot

01 · THE AGENT

The agent does the work.

Prepare a purchase, update an account or complete a task on someone’s behalf.

YOUR BUSINESS
Approval policy

02 · YOUR BUSINESS

Your business sets the boundary.

When policy requires approval, pause the action and give the person a secure handoff.

Soliton liveness primitiveSOLITON
Liveness

03 · THE PERSON + SOLITON

A real person approves.

Review the exact action and give consent. Soliton verifies live presence using physics.

x401
Signed proof

04 · BACK TO THE AGENT

The agent carries on.

Validate signed x401 proof, then let the agent continue within its permissions. Keep the result linked to the approval.

A declined, expired or changed request cannot proceed on the original approval.

Muse and Grok Bot illustrate the agent journey.

SEE IT IN ACTION · 2 MIN

One handoff.
A connected journey.

An agent reaches checkout. The business asks for a person’s approval. After consent and a live presence check, the agent resumes and the business can trace the outcome.

Recorded sandbox with Muse. No payment or shipment.

Read the demo journey
  1. Muse prepares a sandbox order. The merchant detects an automated browser and pauses checkout for human approval.
  2. The person receives a secure link, reviews the order and gives consent for that purchase.
  3. Soliton verifies live presence and connects the accepted result to the order. Faces are blurred in the recording.
  4. The agent resumes under its own approval controls and completes the simulated checkout.
  5. The business sees the request, decision, consent, verification and completion in one history, with the supporting evidence attached.

THE RECORD BEHIND THE ACTION

Who approved what.
And what happened next.

An approval is only part of the story. Connect the request, the person’s consent and the outcome so your business can understand the whole action.

Soliton issues signed approval proof using x401. Your application validates it before proceeding and links the result to that permission.

Permission is specific and time-limited. A different action requires a fresh assessment. Approval and completion remain distinct in the record.

ONE CONNECTED RECORDConcept
  1. The action requestedWhat the agent intended to do, within your policy.
  2. The permission givenThe exact action the person reviewed and approved.
  3. The presence verifiedPhysics-based evidence of a live person.
  4. The proof validatedSigned x401 permission checked by your application.
  5. The outcome recordedWhat actually happened, linked to the approval.

WHERE THIS FITS

At the moments
that need a person’s authority.

Bring people into the decisions that matter, while letting agents handle the work around them.

Agent-led purchases

Let an agent prepare the purchase. Ask the person to approve the specific order before checkout continues.

Account changes

Confirm permission before an agent changes account access or sensitive settings on someone’s behalf.

Sensitive workflows

Require a person’s approval before an agent shares restricted information or commits an important change.

COMMON QUESTIONS

Useful autonomy.
Clear accountability.

Does every agent action need approval?

No. Your policy determines which actions can proceed, which need human approval and which must stop.

Does this replace the agent’s own approval controls?

No. Soliton provides the business with human approval and presence evidence. The agent still follows its own permissions and approval controls before acting.

Does presence prove a person’s legal identity?

No. Live presence, identity and account ownership are separate questions. Additional identity or account checks can be required by the use case.

Does the agent receive the person’s biometric capture?

The person completes the presence check themselves. The agent receives proof of permission to present, rather than the person’s biometric capture.

What happens if the action changes?

Approval covers the action the person agreed to. A change in scope needs a fresh assessment and any required approval. Expired or invalid proof cannot authorize the action.

ExplicitHuman consent
ScopedAgent permissions
VerifiableApproval records

Put human approval
into your agent flow.

Talk to Founders