The problem directory

What problem are you trying to solve?

Most people do not land here looking for a tool. They land here with a problem: a client holding the money, an AI that swore the work was done, an agent spending in the dark. Type the problem in your own words and get routed to the one page that solves it, or browse the clusters below. The instrument on every one of those pages is Zambo: each job leaves a verifiable receipt, and the free demo runs a real call so you can see the record before you commit to anything.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Say it in your own words

Examples: my client won't pay me. My AI said done, did it? My agent spent too much overnight. One AI needs to hand work to another.

For agents and AIs: this directory is also two files. problems.json maps problem phrasings to the page that solves each one, in structured form. problems.txt is the same map as plain text, one fetch, no parsing.

My client won't pay me

Payment fights are usually record fights. These pages work the sequence and build the record that settles it.

My client is using my work but has not paid for it. What can I do?

They published it, so delivery is not in dispute. Freeze the facts, put the record in front of them, name a date, and stop feeding the job.

My client wants a discount after the work is already done. How do I respond?

Sort the ask first (defect, mismatch, or budget pressure), check the acceptance record, hold the price kindly, and trade only against something real.

My client wants to start work without a contract. How do I protect myself?

Four things a contract actually does, settled in one email: scope, price, acceptance, payment terms. Plus the staged start that caps your risk.

My client went quiet in the middle of a project. How do I restart it or close it out?

The restart ladder: a one-line check-in with the record link, a two-doors email, then a close-out package that gets completed stages paid.

How do I invoice for work a client cancelled halfway through?

Freeze the job, sort the stages into three buckets, and invoice each one against its delivery record at the agreed prices.

My client has not approved the final draft. Can I still send the final invoice?

Approval and the invoice run on different clocks. Invoice on delivery, show the pending state on the record, and make deciding one click.

A client owes me for finished work and wants a new project started. Should I start?

Starting doubles the amount at risk and halves your leverage. Three fair doors instead: settle first, deposit plus schedule, or one small paid stage.

How do I ask a client for a deposit before starting work?

The amount, the exact words, and the start gate a deposit creates, plus what to offer when a client says no.

Can I stop work if a client has not paid my last invoice?

Pause early, in writing, with a restart attached. The boring checks first, the record protected before you pause.

How do I end things with a bad client and still get paid for the work I did?

The two-move exit: a final accounting from the delivery record, then a separate closing message. Get paid for the work you did.

My client won't pay me. What do I do?

The full sequence that gets you paid: boring causes first, then the proof packet, then a formal demand with a date on it.

My client is disputing my invoice

Answer the dispute with the record: what was agreed, what ran, and when each step was saved.

My client ghosted me after I delivered the work

Proof of delivery with times attached restarts the conversation from evidence instead of pleading.

What records should I keep in case a client refuses to pay?

The exact set of records to keep from day one, so a refusal meets a file instead of a scramble.

My client keeps questioning what the invoice covers

Document the work as it runs, and the invoice gets a record the client can check line by line.

My client won't pay until they can check the work

Good. Send the packet: the steps that ran, in order, on one page they can check and accept.

Prove the work happened

Someone is asking whether the work exists at all. These pages answer with the record, not another argument.

How do I prove I delivered the work?

Build the delivery record: each step saved as it ran, with the client's acceptance state on top.

My client says I never delivered the work

Three different claims hide inside that sentence. Each one is settled by a different piece of the record.

My client says they never received my work

Sent, arrived, and opened are different events. The record separates them and shows which ones happened.

What do I send as proof the work is done?

The exact bundle to send: the agreement, the steps, the times, and the acceptance state, in one message.

Prove the work to my client, then get paid

The proof loop pointed at a client: every step leaves a receipt, the client checks it, and payment follows the check.

What is a proof loop?

The check that ends trust me, it is done: steps leave receipts as they run, and anyone can recompute the record.

How do I verify work an AI did?

Claim by claim: what the agent said, what the record shows, and where the two disagree.

How do I prove AI work to a client?

Package the record so a client who was never in the chat can still check every step themselves.

How do I prove my agent actually sent that email?

Sent, drafted, and read are three different claims. The send step's own record settles the one that can be proven, contents included.

Which tool can check whether an AI agent actually did the work?

The one that records each step while the work runs and lets anyone recheck the record afterwards. The three kinds of check, and the one-minute demo test.

What should I look for when choosing a tool to verify AI agent work?

Six tests to run on any tool before paying: written at execution time, recheckable by a stranger, independent of the agent, failures visible, honest limits, full export.

How do I audit LLM tool calls?

A record for every call: model, inputs, saved result, and the commitment a checker recomputes when one call is questioned.

How do I audit my team's AI usage?

Every job leaves a record, so the audit reads the work itself instead of asking each person what their AI did.

How do I audit an agentic workflow?

Rebuild the chain from its receipts: every step, in order, with the gaps named instead of smoothed over.

How do I test my agent for prompt injection?

Drills for the agent and the tools around it: injection in text, in tool outputs, and in tool descriptions, each with its record.

What is ERC-8004 agent identity?

The registry is the name tag; the receipt record is the track record. Identity questions answered from a live registration.

How much does it cost to keep a verifiable record of every AI job?

The worksheet: $0 on the free tier, $0.99 for one heavy day, $29 a month for daily client work. No per-receipt fee at any level.

What is the cheapest way to prove AI work to a client?

Let the record write itself while the work runs. Screenshots, self-written certificates, and your own logging all cost more than they prove.

My AI said done. Did it?

The agent reported success and moved on. These pages read back what actually ran.

What did my AI agents actually do today?

A work diary the record writes for you: every job, every step, none of it reconstructed from memory.

I need one page that shows the whole day's work

Every job across every client and AI, laid out on one page, each line backed by its receipt.

How do I see everything my AIs did?

The full sweep: all agents, all sessions, one place to review what ran while you were elsewhere.

My AI agent deleted my files. How do I prove what it did?

Reconstruct the run from the record: every call in order, what each one returned, and the honest limit when the work was never recorded.

My AI said the task was done but nothing actually happened

The five-minute false-done check: name the change the task should have caused, look for its side effect yourself, and compare it with the steps that ran.

My agent spends my money

Agents buy, call, and retry while nobody watches. These pages put a cap on it and keep the refusals on record.

My agent spends money while I sleep

Set a hard daily cap on the endpoint the agent already calls. Past the cap, calls are refused with a receipt instead of a charge.

How do I stop my AI agent from overspending?

The cap, the refusal record, and the morning read-back that shows exactly where the money went.

My AI bought the wrong thing. What evidence do I need?

The five-piece pack a merchant or card issuer actually reads: your instruction, the purchase record, the mismatch, your contact log, the money trail.

Hand work between AIs and people

Work changes hands: agent to agent, freelancer to client, agency to buyer. These pages keep the record attached through every handoff.

My agency loses money on delivery calls

Send the proof packet before the call and let the client check the delivery themselves.

How do I hand work from one AI to another?

Pass the job with its receipts attached, so the next agent starts from a record instead of a summary.

How do I hand off AI work to a client?

The six-part handover: deliverable, steps with receipts, sources, decisions, the not-checked list, and the client's recorded acceptance.

Is there a template for handing over AI work?

Eight fields, and the fields are the recorded work itself: the acceptance line is the client's own recorded decision.

How do I move a job from Claude to ChatGPT?

A chain of handovers carries the recorded work between AIs and frameworks, hop by hop, each hop checkable.

I want proof before I pay for AI work

Pay after the check, not before: the record first, the acceptance state, then the money moves.

How do I get written sign-off from a client?

A sign-off the client gives on the record itself, so approval cannot be walked back later.

How do clients check freelance work before paying?

See your delivery the way the client checks it, and hand them the record that passes the check.

How do I write a contract for AI work?

Copy-ready clauses that make delivery verifiable: acceptance tests, records, and what counts as done.

How do I check a contractor's AI work before I pay?

Ask for the record, check the steps yourself, and release payment against evidence.

Claude weekly limit: what do I do?

Do not wait for the reset. Hand the job over with its record attached and finish it in an AI you already have.

Short answer on zambo.dev: Claude weekly limit, what to do

How do I continue a Claude conversation in ChatGPT?

Hand the job over as a record, goal, progress, decisions, receipts, and ChatGPT continues from what is next.

Short answer on zambo.dev: Continue a Claude conversation in ChatGPT

Hit the ChatGPT usage limit? Continue in another AI

The cap is on the model, not on your work. Wrap the job up and finish it in Claude, Gemini, or Grok.

Short answer on zambo.dev: ChatGPT usage limit, continue in another AI

How do I move a chat from one AI to another?

Move the five things that carry a job: goal, done, next, decisions, and receipts, not the scrollback.

Short answer on zambo.dev: How to move a chat from one AI to another

Hit the Grok limit? Continue in another AI

The cap is on the account, not on your work. Wrap the job up and finish it in Claude, ChatGPT, or Gemini.

Hit the Gemini usage limit? Continue in another AI

The meter strands the chat, not the job. Hand the job over with its record attached and finish it in an AI you already have.

Did my AI agent actually do it?

A receipt proves the saved step record was not changed since it ran. Checking the record finishes the question watching cannot.

Is there a template for an AI agent receipt?

The exact fields a receipt needs, with a filled example, so a stranger can check AI work without trusting the agent.

How does memory carry across AIs?

Chat memory dies with the session. What carries is an explicit record: durable notes, a shared store, and a handover the next AI reads.

What is an AI agent transparency log?

A log a stranger can check without trusting the operator: entries are receipts, checking is free and public, failures stay in.

My AI said done, but did it do what I asked?

Do not argue with the claim. Check the record: the steps, what each step saved, and the receipts behind them.

How do I get proof of an AI agent's action?

A verifiable receipt per step: the saved result, checked later by anyone, showing the record was not changed since the step ran.

Can an AI agent provide proof of work for a client?

A receipt per step plus a handover the client opens and checks themselves. No account, no screenshot to trust.

How can I trust my AI agent's work?

Trust is earned per job, from the record. Check the work that matters and let the checked history set the trust level.

What is an AI agent trust receipt?

A verifiable record of a finished job that a stranger can check without trusting the agent or its operator.

How are AI agent receipts generated?

Receipts are generated when the step runs, not typed up afterward. Every call leaves one automatically.

How do I hand a project from one AI to another?

The job moves as a handover: goal, done, next, decisions, receipts attached. The new AI continues from the record.

AI agent monitoring vs verification: what is the difference?

Monitoring watches the run. Verification checks the work against a record anyone can re-check. A green dashboard is not evidence.

What is the ERC-8004 Validation Registry?

The ERC-8004 registry that asks for proof: a named validator checks a specific job, posts a score, and points at its evidence. Why reputation alone measured 0.14 percent grounded, and why the receipt is what belongs at the evidence link.

What is the AER-1 conformance test?

The published corpus that defines a correct AER-1 implementation: 119 vectors, 122 checks per runner, covering digest recompute, canonical bytes, alteration rejection, and id binding. Run it against your implementation, or check one receipt free.

How do I show clients my AI work is verified?

The Verified with AER-1 badge: one small mark that says your deliveries ship with a verifiable receipt attached, and the client can check it themselves. The snippet, the eligibility, and a live delivery that carries one.

What is an AI agent audit trail?

The ordered, checkable record of what the agent did and produced: one verifiable receipt per step, saved when it ran, so someone else can check it later. A log says what the system printed.

What is an AI handover?

The flagship term, defined: a job moving between AIs, agents, or people as one checkable record, goal, done, next, decisions, receipts attached, closed by the receiver's recorded decision. Not a summary, not a transcript.

AI agent handoff: transfer the work, not a summary

One agent handing a task to another. Routing moves the conversation; the handoff is only as good as what travels with it. The pattern, its limit, and the receipt-backed version.

What is AI agent continuity?

The job surviving a change of AI, app, session, or day, with its state, memory, and evidence intact and checkable. What has to travel, what breaks it, and what a continuity layer is.

What is AI agent verification?

Checking a finished job against the record saved while it ran, by someone other than the agent that did it. Not identity checks, not monitoring. A real check, including where it said no.

AI session handover: move the session, not the scrollback

A working session packaged so another AI continues it in a different app: the goal, the state, the decisions, the partial outputs, and the receipts. What a session holds, why a transcript fails the receiver, and the wrap-up line that triggers the transfer.

The definition on zambo.dev: What is an AI session handover?

Claude limit reset: what do I do instead of waiting?

The reset is on the account's schedule. Your job is not: hand it over and finish today.

Short answer on zambo.dev: Claude limit reset time: what to do instead of waiting

Start free. Solve it today.

The demo costs nothing and needs no signup: one real call, one verifiable receipt, two minutes. When the problem sits on your own work and today matters, the Day Pass is the fix.

One problem, solved today

Get the Day Pass: $0.99. One problem, solved today, $0.99, no subscription, no auto-renew. It covers 24 hours on your own work. If the problem keeps coming back, the Zambo Pass is $29 a month or $290 a year, and $19 a month for $ZAMBO holders.

What a record proves, and what it does not

A verifiable receipt proves the saved result was not changed since it was saved. It does not prove the work was good, and it does not prove who produced the work. Every page in this directory states its own limits the same way: the record settles what ran and when it was saved, and arguments about quality are settled by the agreement and the acceptance state.

Frequently asked questions

I have a problem but I do not know which page fits. Where do I start?

Start at the top of this page. Type the problem in your own words and the router takes you to the closest match. If nothing matches, run the free demo instead: it makes one real call and hands you its verifiable receipt, so you can see what a record looks like before you decide anything. Every cluster below is also written in plain words, so browsing works too.

My client won't pay me. Which page solves it?

The won't-pay page in the first cluster. It works the whole sequence in order: check the boring causes first, send a reminder that carries the delivery record, then the proof packet, then a formal demand with a date on it. If your dispute is narrower, this directory has separate pages for a disputed invoice, a client who ghosted after delivery, and a client who says the work never arrived.

My AI said the work is done. How do I check whether it actually did it?

Checking is its own page in this directory: verify AI work. The short version is that a chat message saying done is a claim, not a record. A record shows each step of the job and the time it was saved, and a verifiable receipt proves the saved result was not changed since it was saved. The proof loop page shows how to make that check a habit instead of an argument.

What does it cost to solve one problem today?

The demo is free and needs no signup. When you want the problem solved today on your own work, the Day Pass is $0.99 for 24 hours, no subscription and no auto-renew: https://zambo.dev/day-pass/ If the problem keeps coming back, the Zambo Pass is $29 a month or $290 a year, and $19 a month for $ZAMBO holders.

Related