# Toast through toolfare

> Orders and checks for any business day, a single order down to its line items, payments with tips and card types, and refunds — across every location you connected, answered inside ChatGPT, Claude, Codex or Cursor. Connect Toast to toolfare once; your AI reads it with your own credentials, and every read is free.

Page: https://toolfare.ai/toast

## Use it from your agent

Paste this into Claude Code, Codex, Cursor or any agent with a shell:

> Set up https://toolfare.ai/skill.md, then use toolfare to answer: How many orders did the downtown location do last Friday?

Apps without a terminal connect toolfare as an MCP server: https://toolfare.ai/docs#connect

## Use it from a script

```sh
mkdir -p ~/.local/bin
curl -fsSL 'https://toolfare.ai/toolfare/toolfare.mjs' -o ~/.local/bin/toolfare
chmod +x ~/.local/bin/toolfare
export PATH="$HOME/.local/bin:$PATH"
export TOOLFARE_MCP_URL='https://api.toolfare.ai/mcp'
toolfare login
```

Then connect your Toast account in the toolfare console (https://toolfare.ai/toast#setup); calls fail until it is connected.

Sign in once per machine; the CLI renews the sign-in itself. On a CI runner or another server, create an API key in the toolfare console and set it as `TOOLFARE_API_KEY` instead of signing in. Paid calls on one sign-in or key run one at a time. `--max-cost` refuses a call quoted above that many credits (1,000 credits = $3).

## Tools

### Orders for a business day

Tool: `toast_list_orders`

Order summaries for a business day or time range — opened, paid and closed times, dining option, voids, and each order’s check total.

Ask:
- How many orders did the downtown location do last Friday?
- How many orders were voided yesterday?

### One order, down to the line items

Tool: `toast_get_order`

The full order: every check with its items, discounts, service charges and payments.

Ask:
- What was ordered on this ticket, and what discounts were applied?
- Show me the line items for our largest order last night.

### Checks, with tax and tips

Tool: `toast_list_checks`

Check-level rows across a day’s orders, for split-check analysis and per-check totals, tax and tips.

Ask:
- What was the average check size on Saturday?
- How much did we collect in tips across all checks yesterday?

### Payments, by type and card

Tool: `toast_list_payments`

Payments taken on a business day with type, amount, tip, card type, status and refund status.

Ask:
- How much of yesterday’s revenue was cash versus card?
- List payments over $200 from last night.

### What was refunded, and when

Tool: `toast_list_refunds`

Payments refunded on a given business day, with the original payment date alongside the refund date.

Ask:
- What did we refund yesterday?
- Were any refunds this week for payments from last weekend?

### Also available

- `toast_list_restaurants`: Your locations, with time zone and closeout hour

## Price

Free to read: it is your own account, so toolfare pays nobody for the data and charges nothing per read. No per-read charge to observe. Reads need no purchase. Like every toolfare call, they run only while your balance holds at least $0.003, and that is not spent.

Balances and top-ups are in US dollars. Quotes and `--max-cost` count credits: 1,000 credits = $3 ($0.003 each).

## Use it when

- You want last night’s or last week’s sales without logging into Toast.
- You are checking check size, tips or voids across locations.
- You want restaurant revenue next to the local campaigns that were running.

## Look elsewhere when

- You want delivery-app orders. DoorDash and Uber Eats are separate connections.
- You want to change a menu, an order or a payment. The connection is read-only.

## Limits

- Dates are each restaurant’s local business day, bounded by its closeout hour, so “today” depends on the location and a late-night day crosses midnight.
- Payment and refund reads fetch each payment individually and are bounded by a limit; a busy day may come back marked truncated.
- No menu data is available through this connection.