Meow

This is a reference for the verification API’s payload adapter. For apps you can use inside a Desk, see Desk apps.

venue: meow. Over HTTP, meowapi, meowbank and meowbanking also resolve to it.

What to send

The request body for the Meow endpoint, bare or wrapped in {body} or {transfer}. Meow chooses the payment rail by URL path, and ACH and wire bodies can look identical, so add a rail hint: type, rail or method set to the rail (ach, ach_scheduled, wire, book, crypto), or endpoint set to the path you will call.

`actionType`	Endpoint	Body	`actionFamily`
`ach`	`POST /accounts/{id}/ach`	`{amount, counterparty_id, description, idempotency_key}`	`payment`
`ach_scheduled`	`POST /accounts/{id}/ach/scheduled`	ACH fields plus `rrule`	`payment`
`wire`	`POST /accounts/{id}/wire`	`{amount, counterparty_id, instructions, purpose, idempotency_key}`	`payment`
`crypto`	`POST /accounts/{id}/crypto`	`{amount, static_memo_id or crypto_id, idempotency_key}`	`payment`
`book`	`POST /accounts/{id}/book`	`{amount, to_account_id, description}`	`transfer`
`set_daily_withdrawal_limit`	`PUT /limits/daily-withdrawal`	`{daily_withdrawal_limit}`	`permission`

Without a hint, the rail is inferred from the fields: to_account_id is book, static_memo_id or crypto_id is crypto, rrule is scheduled ACH, instructions or purpose is wire, and description is ACH. A body with only amount and counterparty_id is typed ach, but the summary says the rail is undetermined and a note says an “ACH only” rule cannot be confirmed.

No live lookup

Every Meow read needs the account holder’s API key, which the harness does not hold. Counterparties are opaque saved-contact ids, so the payee’s identity stays unverified unless your rules pin the exact id.

Notes the classifier adds

Amounts are US dollars with up to two decimals, not cents.
Wires are final once sent. The minimum for wires and crypto is $1.
ACH: at most $1,000,000 per transfer, and a description of at most 10 characters. Wire instructions are at most 140 characters.
Scheduled ACH: rrule must be WEEKLY or MONTHLY and include DTSTART. Total exposure is the amount times the number of occurrences.
A missing idempotency_key risks paying twice on retry.
A crypto payout’s currency, network and address come from the saved contact, not the payload, and cannot be reversed.
A book transfer made with a global API key can reach an account of a different entity.
A daily withdrawal limit change applies to every later payment. A limit of 0 blocks all outbound transfers.

Example

const action = {
  type: "wire", // the rail, matching POST /accounts/{id}/wire
  account_id: "acct_123456789",
  amount: "4800.00", // dollars
  counterparty_id: "8c2f6a1e-3d5b-4f7a-9e0c-2b4d6f8a1c3e",
  instructions: "INV-2044 Acme Metals",
  idempotency_key: "wire-20260702-inv2044",
};

const res = await fetch("https://harness.chance.cc/api/v1/intent", {
  method: "POST",
  headers: { "x-api-key": process.env.CHANCE_API_KEY!, "Content-Type": "application/json" },
  body: JSON.stringify({
    intent: "Pay approved vendors only (counterparty ids on file). Max $5,000 per payment. Wires only to vendors we have paid before.",
    venue: "meow",
    action,
  }),
});
const result = await res.json();
if (result.verdict !== "ALLOW") throw new Error(result.reasoning ?? result.error);
// Only now send the payment to the Meow API.

From an MCP client

Instruct the agent to call verify_intent before creating any Meow payment or limit change, with your rules as intent, the exact request body plus its rail as action and venue: "meow", and to act only on ALLOW.

Integrate

Chance verification

Payload adapters

HTTP endpoints

What to send

No live lookup

Notes the classifier adds

Example

From an MCP client

​What to send

​No live lookup

​Notes the classifier adds

​Example

​From an MCP client

What to send

No live lookup

Notes the classifier adds

Example

From an MCP client