Observed by Atlas — nobody has proved they control this domain. Is it yours?
SheetRelay
OBSERVEDTurn a Google Sheet into an API, MCP server, or REST endpoint
- FRESHNESS
- 1.00
- DECAYS BETWEEN READS
- READINGS
- —
- VERIFIED / MEASURED
- VOUCHES
- 0
- SIGNED STATEMENTS
- THREADS
- 0
- FIELD NOTES
- CLICKS · 28D
- 0
- BOT-FILTERED
- FIRST SEEN
- OCT 8
- IN THE FLOW
SheetRelay connects a Google Sheet so that an AI assistant like Claude or ChatGPT and your own code or no-code tools can both read and write it, under rules you set. The spreadsheet stays in Google Sheets, nothing is copied into another database, and you control which tabs, columns, and actions are exposed. It is aimed at people who already keep real work in a spreadsheet, such as orders, stock, bookings, or a calculator, and want to give it an API without building a backend.
Nothing measured yet. A reading is a measurement with its evidence attached — uptime checked, pricing re-read against what the page claims. Raise a checkable claim in a field note below and Atlas will measure it.
2 spreadsheets · 1,000 calls a month · 1 function, from the dashboard only · 1 key per spreadsheet · 1 person
5 spreadsheets · 10,000 calls a month · 3 functions, callable from anywhere · 3 keys per spreadsheet · Email support
20 spreadsheets · 100,000 calls a month · 25 functions · 10 keys per spreadsheet · Keys narrowed to tabs, columns and rows
100 spreadsheets · 500,000 calls a month · 100 functions · 50 keys per spreadsheet · 15 people
Every crawl is diffed. Material changes are listed.
Nobody has vouched for SheetRelay yet.
A vouch says you use it. Your handle, how long, and an optional note.
I use this — vouchHave a question about SheetRelay? Ask the people using it.
No field notes yet. A field note is about use: what broke, what it replaced, what the docs don't say. Anything in one that makes a checkable claim gets measured by Atlas, which replies with the reading.
Outbound clicks are counted for the builder.
Claim it