Skip to content
Agent Process

Agents that work your way.

Describe how the work should go, and your AI agent follows it, with your data, your systems, your emails and the right person’s sign-off, every step on record.

No code, and no new AI to buy. Works with Claude Desktop, Codex, Cursor, OpenClaw and 15 more. Free during the pilot.

Run by your AI agent

Refund request · order #5521

Your agent is working
  1. Your AI agent

    Read the order

    Looking up order #5521…

  2. Jev · decision AI

    Assess the claim

    Next

  3. Your AI agent

    Apply your refund policy

    Next

  4. Priya · Finance

    Approve the refund

    Next

  5. Your AI agent

    Issue the refund

    Next

  6. Your AI agent

    Tell the customer

    Next

On the recordData readAI judgementRoute chosenApprovalSystem updatedEmail sent

Illustrative example

What stops teams handing work to agents

Most teams stop at the same questions. Watch how each one is answered inside the process.
  • Without a processIllustration

    Done! Refund issued.

    Issue the refund · required to finish

    • Refund receiptMissing
    • Amount matches the orderNot checked

    Sent back to the agent

How a refund gets done

You don’t write code or switch AI tools. You tell your agent how the work should go, and what it may use along the way.
  1. First, tell your agent how the work goes.

    You, to your agent

    When a refund request comes in, read the order and have Jev check the claim. Anything over $500 goes to Priya in Finance. Then issue the refund and tell the customer.

    Refund requestDraft process

    1. Read the orderYour AI agent
    2. Assess the claimJev · decision AI
    3. Over $500 goes to FinanceLabelled route
    4. Approve the refundPriya · Finance
    5. Issue the refundYour AI agent
    6. Tell the customerYour AI agent
  2. Then connect what it needs.

    You, to your agent

    Read orders from our orders database. Use the payments API to issue refunds, and our refund template to tell the customer.

    What this process may use

    • OrdersPostgreSQLRead
    • Payments APIRESTIssue refund, in this process only
    • Refund confirmationYour email templateSend to the customer

    Passwords and keys stay with Agent Process. The agent never sees them.

  3. Then let it run.

    You, to your agent

    Handle refund request #5521.

    Illustrative run record

    Refund request · order #5521

    Completed
    1. Your AI agent · orders database

      Order read

      Order #5521 · $740.00 · arrived damaged

    2. Jev · decision AI

      Claim assessed

      Damaged in transit · 94% sure · above your 70% line

    3. Your AI agent

      Route chosen

      Over $500, so the route to Finance; reason recorded

    4. Priya · Finance

      Approved, from email

      Decision + what Priya saw, kept together

    5. Your AI agent · payments system

      Refund issued

      Receipt re_8f2

    6. Your AI agent · your template

      Customer told

      “Your refund is on its way” · send recorded

    Open any run to see what the agent did, the data it used, how Jev judged it, the route it took, who approved and which emails went out. Each organisation’s data is kept apart, and every approval keeps what the person saw.

    Security and boundaries
    What the pilot supports today
    • Agents connect through MCP with an access token. ChatGPT and claude.ai connectors and scheduled starts are not enabled in the pilot.
    • Controls apply to work routed through Agent Process. We do not control an agent’s other tools or guarantee the truth of its reports.
    • Database sources support reads. Enabled REST endpoints support writes. Published email templates support outgoing communication; handling replies is not supported yet.

Priya approves it from her inbox.

The refund is over $500, so the run waits for Finance. Priya gets an email, opens the request with the order and Jev’s assessment in front of her, and decides. She needs no account. Try it as Priya.

Priya’s review inbox

Refund process / Order #5521

Waiting for you
Submitted by your agent Request v1

Refund $740.00 for order #5521

The customer reports the order arrived damaged. Over $500, so Finance decides.

Agent recommendation

Issue the full refund.

Jev assessed the claim as damaged in transit, 94% sure, above your 70% line.

Order
#5521 · $740.00 · delivered 2 May
Jev
Damaged in transit · 94% sure
Route
Over $500 goes to Finance

Assigned to Priya

Finance approval · refund request

You’ll confirm your choice in the next step.

Run record · order #5521

  1. Waiting for approval Assigned to Priya
  2. Issue the refund Waits for the decision

Waiting for you. Opening a request doesn’t decide it.

Interactive illustration · No approval email is sent. Result + evidence + decision

Jev makes the judgement calls

Some steps need judgement: what a customer is asking for, whether a draft meets your standard, whether an application is complete. Jev, the decision AI from TypeSafe built into Agent Process, answers the question you set, against your criteria.
Sort
“Which kind of request is this?” Picks one of your categories, so the process takes the right path.
Score
“How well does this meet our standard?” Rates work on your own scale, from your own descriptions.
Check
“Is this true, given the evidence?” Says how likely a statement is, so weak cases don’t slip through.

When Jev is unsure, a person decides, so unclear never passes on its own. You set the lines, and your process decides what each answer means. Agents can’t submit or overwrite its answers, and each one is kept with the run.

Jev · decision AI

Your question: what is this request about?

Refund request 1 of 4

“The vase arrived in pieces and the box was crushed.”

  • Damaged in transit96%
  • Changed their mind3%
  • Never arrived1%
  • Your line: 70% sure

Damaged in transit

Refund path

0

Changed their mind

Returns policy

0

Unsure

A person decides

0

Illustrative example. You set the question and the line.

No new AI to buy. Agents connect through MCP, the open standard for plugging AI agents into business tools, and setup takes a few minutes. You can also give a client’s or partner’s agent a key to the processes you choose, and pause or revoke it at any time.

Questions

  • Agent Process turns your business processes into steps the AI agents you already use can follow. Your agent does the work with your data, systems and email templates, Jev makes the judgement calls against your criteria, and the right person signs off before anything important. Every step is recorded.

Bring one process.

Tell us the job. When you’re invited to the free pilot, we set it up with you on a call and run it with your agent.

Join the pilot waitlist

Free during the pilot. We ask for your email on the next page.