Guides
Agents without an API, such as Instinct
Some agents publish no API, no MCP support and no admin console you can connect. Instinct is one. Here is what Immiscible can and cannot govern for them, said plainly, and how to set it up.
Instinct (instinct.com, made by Spear Street Technology) is a personal AI assistant you text or call. It works on a computer of its own in the cloud, with a browser and the logins you give it, and can book, buy and write on your behalf. As of October 2026 it is invite only, and its public site publishes no developer documentation: no API, no MCP server, no way to add MCP servers or tools of your own, and no way to point its model traffic at a gateway. Its terms let it enter into agreements and transactions on your behalf.
So there is no Instinct connector in Immiscible, and we will not pretend otherwise. If Instinct publishes an API or MCP support, a connector of the same shape as discovery is the next step.
#What Immiscible can govern
| Rail | Works for Instinct | How |
|---|---|---|
| Money, on a card | yes | Give Instinct a card that only Immiscible can make work: a virtual card on the card rail, or a Ramp card mapped to it and reconciled |
| The kill switch | yes, for money | Freezing the Instinct agent voids its receipts, so its card declines; with Ramp lock on freeze, its Ramp card is locked too |
| Evidence | yes | Every authorisation, approved or declined, and every reconciled charge is on the ledger against the Instinct agent’s id |
| Each request, before it is made | no | Instinct does not ask the gate, so Immiscible cannot judge a request with what shaped it in view |
| Model traffic | no | Instinct runs its own models; the gateway never sees that traffic |
| Tools and data | no | Instinct cannot be pointed at the MCP proxy; release vault data to it by hand, not through a data mandate |
#Set it up
- Register the agent. Under Agents (or Add an agent in a personal workspace), add an agent named Instinct with vendor
custom. It gets a stable id like any other. - Give it its own card. Bind a virtual card to it on the card rail, and give Instinct that card and no other. At the card, the issuer asks Immiscible before each charge; with no receipt, the charge is declined.
- Ask before you tell it. Because Instinct does not ask the gate, you ask on its behalf: use the agent’s key (from your phone, a shortcut or the MCP server in Claude) to request the payment before you text Instinct to make it. The mandate, the never-pay list and the allowance judge the request, you approve it on your phone if it is above your line, and the receipt it gets is what lets the card work for that payee and amount.
- Or reconcile after. If Instinct holds a Ramp card instead, map the card to the Instinct agent. Every charge is reconciled against its receipts, and a charge nobody allowed shows as unmatched and is recorded as an incident.
- Stop it. The kill switch freezes it with everything else.
#Why this is still worth doing
An agent that can spend is governed at the money even when it cannot be governed at the request. The card rail turns “it has my card” into “it has a card that works only for what I said yes to”, and the ledger keeps the record a bank statement will not: who allowed each payment, under what, and when.