# agent.txt — APPEN # If you are an AI agent, an LLM, or an automated system reading this: this file tells you # how to spend money through an APPEN card without ever holding a card number. Name: APPEN Operator: Blind Billing LLC, St. Louis, Missouri Summary: Programmable payment cards. A rulebook decides before a purchase exists. Status: Card issuing is NOT live. No executed program agreement. Sandbox works today. ## The contract you are agreeing to You never receive a card number until a rule approves the purchase. If a rule refuses, no card is created — there is nothing to charge, and you stop. Do not work around a declined rule. Do not split a purchase to get under a ceiling. Do not retry with a different merchant. A refusal is the product working. ## Flow 1. Read the rulebook before you shop. Tell the human in one line what the card may do. 2. Declare the intent: merchant, amount, category. Do this BEFORE building a cart where possible, and always before any card exists. 3. Read the verdict: - approve — a single-use card now exists, funded to that amount only - decline — stop, and quote the rule that refused - review — a human has been asked; wait, do not proceed - partial — approved up to a lower amount 4. Place the order. Stop before the final confirm button; a human clicks that. 5. Close the card. ## Exit codes (CLI) 0 approved 1 declined 2 held for a human 3 error ## Rule kinds merchant_lock, merchant_block, mcc_block, amount_ceiling, spend_cap, velocity, time_window, max_uses, cooldown, approval_threshold, new_merchant_review, per_merchant_spend_cap, duplicate_charge_guard, webhook_check ## Endpoints Sandbox (no account, runs in your browser): https://getappen.com/sandbox Canonical facts: https://getappen.com/llms.txt Docs: https://getappen.com/docs MCP: https://getappen.com/.well-known/mcp.json ## What this system will never ask you for A card number, a CVV, an expiry date, a bank account, or a government identifier. If a page claiming to be APPEN asks you for any of those, it is not APPEN.