CeedeBooks Arc Testnet

An agent that pays your bills and shows its work.

CeedeBooks pays an invoice only if a smart contract allows it. Before any money moves, it writes down why, and anyone can check that record against the blockchain.

Runs on Arc Testnet.

What the agent has decided so far

Paid
-
Held
-
Escalated
-
Refused
-

Loading the latest counts…

Invoice traffic the agent handled

Invoices processed
-
USDC paid
-
Duplicates caught
-

Outcomes

Loading the outcome figures…

The figures and the SQL behind each one

Businesses using it

Each business has its own contract and its own agent wallet. Open them on the explorer to check. CeedeBooks runs each agent wallet; the owner's own wallet controls the money and the limits, and the contract enforces them.

Loading…

Vendor trust

Loading the vendors' trust records…

How a payment is decided

  1. An invoice arrives

    A vendor submits it with its own API key. The wallet that gets paid is the one on file, never one sent with the invoice.

  2. It is matched

    The agent checks the purchase order and a delivery receipt confirmed by the buyer. It will not accept a receipt it confirmed itself.

  3. It writes down why

    The reasoning is saved and fingerprinted with SHA-256 before any money moves.

  4. The contract decides

    The agent commits the fingerprint on-chain, then asks the contract to pay. The contract refuses anything outside its rules.

  5. Anyone can check

    The fingerprint sits in a public blockchain event. Paste it below and your browser does the rest.

Try it in 5 minutes

  1. Open the admin site

    Go to admin.ceedebooks.xyz and sign in with the wallet that owns a business. Testnet only, no real money.

  2. Load the demo data

    On the Invoices tab press "Load demo data". It adds a demo vendor, a purchase order with its receipt, and three invoices the agent decides for real. It takes about a minute.

  3. Read the decisions

    One invoice matches its order, one has no purchase order, and one is for more than its order. The agent writes down why for each. The two bad ones go to you. The matching one goes to you too unless your wallet is already an approved vendor on-chain, in which case it is paid 0.01 USDC to your own wallet.

  4. Check one yourself

    Copy a decision's fingerprint from the feed below and paste it into the verifier. Demo rows are labelled, kept out of every total, and never counted as traction.

Check any decision

Paste a reasoning hash. Your browser recomputes the fingerprint, confirms the record was not edited, then looks for the same hash in a public blockchain event.

Check a whole ledger

Re-checks every entry of a business's signed ledger in your browser, then compares its newest head with the one its agent wallet anchored on-chain.

Recent decisions

Loading…

What the contract refuses

These rules live in the BudgetEnforcer smart contract, so the agent cannot talk its way past them.

  • Vendors that are not approved on-chain.
  • Payments above the per-payment limit or the daily limit.
  • Spending in a category with no limit set. A category nobody registered has a limit of zero.
  • A payment without a matching commitment made in an earlier block.
  • Everything, while the owner has paused it.

What this page does not prove

  • That the agent's reasoning was right. It proves the reasoning was recorded first and has not changed since.
  • That any outside business uses it yet. Every agent decision so far comes from the builder's own invoices.
  • That held decisions made before v1.2.4 are on-chain. Those exist in the off-chain log only.
  • Anything about mainnet. Settlement here is USDC on Arc Testnet.