For Agents
Givvy, for the assistant doing the shopping work
Shoppers increasingly send an AI agent to do the checking. Givvy is built for that from the start: the same verified records these pages render are published for agents to read, and a permission ladder governs anything beyond reading.
The permission ladder
Public read
No grant needed. Offers, programs, and listings — the same public pages and structured records a person reads. Read it freely; quote the verification line with it.
Scope: the public catalog, including verification state and last-verified date on every record.
Delegated read
With the member’s grant, an assistant reads that member’s own wallet — saved offers, memberships, reward balances — and checks offers against a planned purchase before money moves.
Scope: one member’s wallet, read-only, under a grant the member can revoke at any time.
Scoped writes
Acting is previewed first, confirmed, and receipted: save an offer, connect a pass, spend rewards, or enter a sweepstakes. Anything that spends value or enters a contest requires human confirmation at the moment of the act — a standing grant is never enough.
Scope: the named act only. Credentials never pass through an agent conversation.
Sweepstakes sit inside the ladder, not above it: an agent enters a listing only where the listing’s own record permits it, under the member’s grant, up to the frequency the official rules set — the ceiling, never past it. Where the record prohibits agent entry, or says nothing, the agent does not enter. permitted is the only yes.
STAGE: LISTED — READ API, MCP SERVING, AND DELEGATED ACTIONS IN DEVELOPMENT. PUBLIC PAGES AND STRUCTURED DATA ARE LIVE.
What agents can call
Read the catalog
Every store, offer, program, and sweepstakes listing on Givvy — the same records these pages render.
Read API · MCP · public pages
Check before a purchase
Ask whether a live offer applies to a basket before your person pays.
Read API · MCP
Read a wallet with a grant
With the member’s grant, an assistant reads that member’s own wallet: saved offers, memberships, reward balances.
Delegated read API
Act with a grant
Save an offer, connect a pass, or enter a listing on the member’s behalf — within the permission ladder, and always with a receipt.
Delegated write API
Enter sweepstakes under permission
Where a listing’s record permits agent entry, up to the listing’s own frequency — the ceiling in the official rules, never past it.
Delegated write API
Each capability is labeled with its honest stage: Callable works today; Listed is specified and published, in development — not callable yet.
The machine layer, in the open
Every page on this site declares its machine-readable forms in its head. This page’s own declarations:
<link rel="alternate" type="text/plain" href="/llms.txt" title="Givvy — summary for language models">
<link rel="alternate" type="application/json" href="/data/catalog.json" title="Givvy catalog — public records">
Machine summary for this site: https://getgivvy.co/llms.txt
Sitemap: https://getgivvy.co/sitemap.xml · Robots: https://getgivvy.co/robots.txt
Honest limits
Unverified offers never display as verified. A record carries its verification state on its face, and agents must carry it too — an offer quoted without its state is a misquote.
Dates are records, not promises. An offer’s window comes from its record; if the record is stale, the honest answer says when it was last verified.
Credentials never pass through an agent. Grants are issued and revoked by the member in their account; an agent holds a scoped grant, never a password.
Read the machine summary (llms.txt) Read the full text (llms-full.txt) Browse the public catalog (JSON)