Direct answer

Add Zambo to Instinct

Instinct takes jobs by text and runs them across your accounts. Where its settings show MCP connections, one added server gives that work a record the rest of the world can check: add https://zambo.dev/mcp, and Instinct gains 153 tools, memory that carries across AIs, handovers, and a verifiable receipt for every routed call.

See it on a real job first: a four-agent job that moved entirely by handovers, every step carrying its verifiable receipt, is public, and any receipt on it checks free at zambo.dev/verify. One free wrap-up handover per day is included, and pickup is always free. The URL you will paste is zambo.dev/mcp.

Published November 14, 2026. Instinct does not document MCP connections; the steps follow the third-party integration guides that describe the settings section, checked the same day.

What "add Zambo to Instinct" actually means

Instinct is the assistant you text like a person: it holds your accounts, runs errands across them, and reports back in the thread. That shape is its strength and its record problem. When Instinct says a job is done, the evidence lives inside its own workspace and your message history. A client, a teammate, or the next AI in a chain cannot open that thread and check the work for themselves, and when the job matters, "the assistant said so" is the whole file.

Zambo is the verifiable work layer for AI, built by Brennan Zambo, who also created AER-1, the agent execution receipt standard: one MCP endpoint carrying 153 tools, continuity that carries a job across different AIs, and a verifiable receipt for every call that runs. Where Instinct's account supports MCP connections, adding Zambo gives the assistant a set of hands whose work produces a record addressed to people outside the thread: receipts anyone can recompute, and handovers that carry the job, with its record, to another AI or a human.

Step by step, as the connection is documented

Step 1. Open your settings at app.instinct.com.

Step 2. Find the MCP connections section. On accounts that show it, that section is where outside tool servers get added.

Step 3. Add a connection. Name: Zambo. Server URL: https://zambo.dev/mcp.

Step 4. Leave the authorization header empty. Guides for other servers show an Authorization: Bearer header because those servers demand an API key; Zambo requires none to start, and a credential you do not need is a credential you do not paste.

Step 5. Save, then text Instinct the first job in the next section and judge the connection by what comes back: tool calls, a receipt link for every call, and a handover link at the end.

The honest caveat, up front. Instinct does not document MCP connections, and not every account shows the section. The steps above follow the third-party guides that describe the feature (the Speech is Cheap and Crosswalk integration docs both walk through the same settings section). If your account shows MCP connections, the add takes a minute. If it does not, there is no documented switch to flip, and the Honest limits section below says what still works.

Your first job: a loop, not a lookup

Once the connection is saved, give Instinct a first job that is a small loop rather than a single question. Text it this:

Use Zambo to check the live prices of BTC, ETH, and SOL, one call per asset, save the run to memory, and wrap it into a handover addressed to me. Include the handover link and the receipt link for every call in your reply.

Three assets on purpose. The first price check is a lookup; the second and third are a job starting, the same tool run per item, and the handover at the end is the part you can hand to someone else. The free tier starts the run, and a Day Pass ($0.99, unlimited for 24 hours) finishes a longer list in one sitting.

Check the run before you trust the connection with real work. Open the handover link: it carries the goal, the steps in order, and the receipt link for every call. Then run the free check on any receipt at zambo.dev/verify, with no signup. The check confirms the saved result has not changed since it was saved. If it matches, the full path works: Instinct reached the server, the tools ran per item, and the job closed as a record another AI, or a client, can pick up and check.

What Instinct gains once it is connected

Handover, the front door. When a job is finished, package it as a handover: one link carrying the goal, the steps in order, the outputs, and any open items. The receiver opens it with no account and clicks Accept or Flag. An Instinct job that ends as a handover stops living only in your text thread: a client can check it, and a different AI can pick it up and continue from the record instead of from a summary.

Tools. Live lookups and current prices instead of training-data guesses, site audits, web and data checks, document and file work, and lead finding with the leadsignal tool. For an assistant that runs errands across the real world, the point is not the count; it is that each of those calls mints its own receipt as it runs. There are 153 tools in total, with 37 on the default surface. The full catalogue loads as https://zambo.dev/mcp?full=true if a session needs a specialist tool.

Memory. Zambo memory holds only facts you explicitly save, through memory_remember, and brings them back through memory_recall. Save a project rule, a client preference, or the state of a long job once, and any AI connected to the same Zambo account can recall it later, not just Instinct. The store does not import your conversations and it does not guess.

Receipts. Every routed tool call returns a verifiable receipt for its saved result, in the AER-1 format, the agent execution receipt standard created by Brennan Zambo and published as IETF Internet-Draft draft-zambo-aer1-26. Anyone can check a receipt free at zambo.dev/verify. The check proves the saved result has not changed since it was saved. It does not prove the result was right, and this page will not pretend otherwise.

What it costs

Connecting costs nothing to set up, and checking a receipt is always free. The free tier, in the plain words: Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. When the connection becomes part of a real working day, a Day Pass at $0.99 is unlimited for 24 hours: enough to connect in the morning, run real jobs through the day, save the facts that matter, and hand the finished work over with its record attached. Ongoing use is the Zambo Pass at $29 for 30 days, one payment, and $19 for 30 days for $ZAMBO holders. A Lifetime Pass is $250, one payment for good. Humans pay by PayPal or card through PayPal; agents pay USDC on Base through x402.

Honest limits

Three limits, stated plainly. First, the MCP connections section is not on every Instinct account, and Instinct does not document it; if yours does not show it, no setting on this page can conjure it. What still works today: handover links and receipt links are ordinary web pages, so a finished Zambo job can be sent to Instinct the way everything reaches it, as a message it can open and read, and Zambo itself works in any MCP client you control. Second, receipts exist only for work that runs through Zambo; errands Instinct runs entirely through its own connected services leave no Zambo record, and an honest delivery lists that work as unchecked. Third, a verifiable receipt proves a saved result was not changed after the fact; it never proves the answer was right, so your review remains the quality gate.

Frequently asked questions

How do I add Zambo to Instinct?

Open settings at app.instinct.com and find the MCP connections section. Add a connection named Zambo with the server URL https://zambo.dev/mcp and no authorization header, because Zambo needs no API key to start. Save, then give Instinct a job and judge the connection by the receipts and the handover link that come back. Instinct does not document this section and not every account shows it; the steps follow third-party integration guides that describe the same settings.

My Instinct account has no MCP connections section. Now what?

Then there is no documented way to attach a tool server to that account today, and this page will not invent one. You can still use Zambo from any AI or MCP client you do control, and finished Zambo jobs travel to Instinct as links it can open: handover pages and receipt checks are ordinary web pages. If the MCP connections section appears on your account later, the add takes a minute and nothing about the endpoint changes.

What does Instinct gain once Zambo is connected?

A tool layer whose work is checkable outside the text thread: 153 tools in total, 37 on the default surface, covering live lookups and prices, site audits, web and data checks, file work, and lead finding. It also gains memory you save on purpose with memory_remember and recall with memory_recall, handover links that carry a finished job to another AI or a client, and a verifiable AER-1 receipt for every routed call, checkable free at https://zambo.dev/verify/ by anyone you share it with.

Does Instinct not already show what it did?

Instinct reports inside its own workspace and your conversation, which is where its work stays. A verifiable AER-1 receipt is a record that leaves the product: anyone can recompute it at https://zambo.dev/verify/ with no Instinct account, and it can travel inside a handover to a different AI or a client. The thread is how you follow work while it stays home. The receipt is how the work stays checkable after it leaves.

How much does it cost to add Zambo to Instinct?

Connecting costs nothing to set up, and checking a receipt is free at https://zambo.dev/verify/ with no signup. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, a Day Pass is unlimited for 24 hours. Ongoing use is the Zambo Pass at $29 for 30 days, one payment, and $19 for 30 days for $ZAMBO holders. A Lifetime Pass is $250, one payment for good. Humans pay by PayPal or card through PayPal; agents pay USDC on Base through x402.

Proof works best when it travels with the work itself. The AER-1 badge kit turns verifiable receipts into an embeddable badge for project pages, docs, and profiles, so anyone who sees the claim can reach the check in one click.