Skip to content

A clear path from invoice
to payment.

Explore the flow

Sandbox environment. No real money moves.

BUILT AROUND YOUR CONTROL

PDF to structured invoices

Rules before payouts

Decisions you can trace

Less chasing.
A little more flow.

From a stack of vendor invoices to a clear next step. Three stages, with your rules running through all of them.

01

Bring the invoices.

Upload a PDF containing your vendor invoices. Bring the details together before any payment begins.

ONE DOCUMENT. A CLEAR START.
02

Draw the boundaries.

Register trusted recipients and set payment limits. Give the agent a defined space to work in.

YOUR RECIPIENTS. YOUR LIMITS.
03

Follow every decision.

Let eligible invoices move to sandbox payout. Review the exceptions and see why each decision was made.

NOTHING LOST IN THE HANDOFF.

What happens
before a payout?

Reading an invoice and authorizing a payment are separate jobs. AgentPay keeps that distinction visible throughout the workflow.

See the controls

The agent reads and proposes.

Invoice details are extracted from your PDF into structured records. The agent proposes a next step for each invoice, with a reason you can inspect.

A proposal does not authorize a transfer.

Your rules decide what can proceed.

Registered recipients, payment caps, and the monthly budget are checked before execution. The model cannot choose a different payout amount or destination.

The payment boundary is enforced in code.

You review the exceptions.

Inspect invoices that need attention and the reasons behind their decisions. Follow eligible payments through PayPal sandbox and check their payout status separately.

Eligible for payout does not mean paid.

Give your agent
room to work.
Not room to guess.

Automation works better with a clear set of rules. Define what can move forward, and keep exceptions where you can see them.

Set your guardrails
THE CONTROL LAYERYOUR RULES
01

Known recipients only

Keep payouts tied to recipients you have registered.

02

Limits before execution

Define payment boundaries before the agent runs.

03

Exceptions stay visible

Review invoices that need a closer look.

Bring a small batch.
See the whole process.

AgentPay is a sandbox for testing invoice-to-payment workflows. Here is what to prepare for your first run.

Your document
A PDF with selectable invoice text.
Up to 4 MB and 200 pages. Scanned images and OCR are not supported.
Your recipients
Register who can receive a payout.
Set your payment limits and monthly budget before running a batch.
Your sandbox
Connect PayPal sandbox credentials.
USD only. Live credentials and real-money transfers are not supported.

Built for developers exploring controlled agent payments and reviewers who need to understand each decision.

Read the setup guide

Clarity before
you begin.

A small workspace.
A deliberate way to pay.

Does AgentPay move real money?

No. This version runs in a sandbox environment. You can explore the invoice-to-payout workflow without moving real money.

What do I need to get started?

Sign in with Google, register your recipients, and set your guardrails. Then upload a PDF containing your vendor invoices to start a batch.

What happens when an invoice needs attention?

Invoices that need review remain visible in your workspace. Inspect the reason for each decision before taking the next step.

Can I inspect the source code?

Yes. AgentPay’s source is available on GitHub. Use the Source link in the navigation or footer to explore the implementation.

Your next batch.
A clearer way forward.

Start in the sandbox. Stay in control.