Skip to content
Menu

tab

AI Agents

Is this your project? Claim and verify →

Give your agents spending power. Pay-per-request APIs over HTTP 402, capped by signed mandates, settled in USDC on Robinhood Chain.

What HEY knows

Building
Shipping consistentlyShipping: 7 meaningful events in 30 days; latest ship 4 days ago. Evidence Source

Build Momentum 60How it is measured

Latest ship
Code changes, week of 2026-10-19 – 2026-10-25 · 56 commits
Latest change
Derived2 days ago: 3 meaningful ships in the 7 days to 26 Oct, 1 the 7 days before. Evidence

HEY’s own reading

What this change is
What it names
HEY’s own reading names no capability.
Stage
HEY’s own reading of the record, not something the project shipped.
Reported by
HEY’s reading of the record. HEY’s own reading of the record: nothing to corroborate.
Release and deployment
Not a release or a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it 2026-10-26; HEY first knew on 2026-10-26.
Not known
  • No source HEY holds names what this change does.

Evidence: signal record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts tab on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me tab’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Token market · context
No token tracked
Not yet known
Unknown2 gaps: Published packages (not enough yet), API description (not enough yet). Packages name its repository, but none is confirmed as the project’s own.

HEY can answer 8 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 7 meaningful events in the last 30 days, the newest 2026-10-24.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-19 – 2026-10-25 · 56 commitsv2.4.0: tab speaks x4022.2.1+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source3 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-10-19 – 2026-10-25 · 56 commitsv2.4.0: tab speaks x4022.2.1+4 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-10-19 – 2026-10-25 · 56 commits

Code activitySource linked

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

What changed, in the repository’s own words:

6 active days in paidwithtab/tab.

This week HEY looked inside 3 of 56 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

Record ship:375054fe… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗ (opens in a new tab)

Shared change · Development spike

tab: 3 meaningful ships were recorded in the latest 7 days, from 1 in the 7 days before.

Builder status: Shipping.

Dated 2026-10-26 by the sourceSource: HEY Signal

View evidence ↗Evidence receipt

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about tab — as of 28 Oct

Is tab still being built?
DerivedShipping: 7 meaningful events in 30 days; latest ship 4 days ago. Evidence
What did tab ship last?
FactCode changes, week of 2026-10-19 – 2026-10-25 · 56 commits — Code activity, 4 days ago. Evidence
What does HEY not know about tab?
Unknown2 gaps: Published packages (not enough yet), API description (not enough yet). Packages name its repository, but none is confirmed as the project’s own. Details

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. 4 releases in paidwithtab/tab on 23 Oct

    GitHub release

    Show all 4 releases

    1. v2.4.0: tab speaks x402

      GitHub releaseSource verified

      tab now speaks x402, the HTTP 402 payment standard Coinbase started and Cloudflare, Visa and Mastercard build on. Both directions. x402 buyers can pay a tab gateway · On the evm rail, every 402 carries x402 requirements (PAYMENT-REQUIRED, version 2, exact, EIP-3009) next to… Show all
      • tab now speaks x402, the HTTP 402 payment standard Coinbase started and Cloudflare, Visa and Mastercard build on. Both directions. x402 buyers can pay a tab gateway
      • On the evm rail, every 402 carries x402 requirements (PAYMENT-REQUIRED, version 2, exact, EIP-3009) next to tab's own challenge.
      • The gateway checks the signed transfer (amount, recipient, time window, signer, then a dry run on chain), calls the upstream, and settles from a small gas wallet (--x402-settler). The answer carries PAYMENT-RESPONSE and a signed tab receipt. If the…
      View evidence: v2.4.0: tab speaks x402 (opens in a new tab)

    2. v2.3.2: security audit fixes

      GitHub releaseSource verified

      A full security audit of the payment path, the Robinhood Chain code, the catalog site and the hosted company service. Every critical and high finding is fixed, with a test that runs the attack. Payments · A payment can only have one encoding (low-s, canonical), so an agent… Show all
      • A full security audit of the payment path, the Robinhood Chain code, the catalog site and the hosted company service. Every critical and high finding is fixed, with a test that runs the attack. Payments
      • A payment can only have one encoding (low-s, canonical), so an agent cannot send a payment the chain will refuse after the call was served.
      • One payment per agent nonce in flight, and a payment that does not settle withholds the response instead of giving it away.
      • The client pins the tokens it pays in and their decimals, and enforces the mandate itself (expiry, realms, per-call cap…
      View evidence: v2.3.2: security audit fixes (opens in a new tab)

    3. v2.3.1: in the MCP registry, and a catalog that stays searchable

      GitHub releaseSource verified

      In the MCP registry. tab's MCP server is listed in the official MCP registry as io.github.paidwithtab/tab (from server.json), and on Glama. Install it from any client that reads the registry; it runs npx paidwithtab mcp, and npx paidwithtab init once sets up a key, a mandate and… Show all

      In the MCP registry. tab's MCP server is listed in the official MCP registry as io.github.paidwithtab/tab (from server.json), and on Glama. Install it from any client that reads the registry; it runs npx paidwithtab mcp, and npx paidwithtab init once sets up a key, a mandate and starter credits. A catalog that stays searchable. A gateway that fails a refresh keeps its last good routes in search for six hours, marked stale, instead of dropping out. GET /v1/health returns the catalog version, the routes it serves and each gateway's state, and answers 503 when search would be…

      View evidence: v2.3.1: in the MCP registry, and a catalog that stays searchable (opens in a new tab)

    4. v2.3.0: signed receipts

      GitHub releaseSource verified

      Receipts now prove what was bought, not just that money moved. Signed receipts (spec draft 0.5) · Every gateway has an Ed25519 receipt key, published as receipt_key in /.well-known/tab. · Each receipt is signed over the mandate id, the challenge id, the exact request the agent… Show all
      • Receipts now prove what was bought, not just that money moved. Signed receipts (spec draft 0.5)
      • Every gateway has an Ed25519 receipt key, published as receipt_key in /.well-known/tab.
      • Each receipt is signed over the mandate id, the challenge id, the exact request the agent signed (query and body hash) and its signature, the response status and body hash, the seller, and the payment ref (the transaction hash on Robinhood Chain).
      • The gateway reads the upstream body before capture, so the response is fixed before any money moves. Checking them
      • client.verify(url, res, body…
      View evidence: v2.3.0: signed receipts (opens in a new tab)

  2. 3 releases in paidwithtab/tab on 22 Oct

    GitHub release

    Show all 3 releases

    1. 2.2.1

      GitHub releaseSource verified

      Catalog: the hosted gateways now serve 123 routes across 59 services, up from 40 across 23. The 36 new keyless services include Robinhood Chain explorer reads and JSON-RPC, Ethereum RPC, Bitcoin via mempool.space, SEC EDGAR, RDAP and DNS, Binance, Kraken, Coinpaprika, DefiLlama… Show all

      Catalog: the hosted gateways now serve 123 routes across 59 services, up from 40 across 23. The 36 new keyless services include Robinhood Chain explorer reads and JSON-RPC, Ethereum RPC, Bitcoin via mempool.space, SEC EDGAR, RDAP and DNS, Binance, Kraken, Coinpaprika, DefiLlama, Bluesky, ClinicalTrials.gov, openFDA, Europe PMC, NVD, OSV, npm, PyPI, endoflife.date, ECB, World Bank, live flights and holidays. Company: a run that reports done while mentioning a colleague hands the ticket to them in review instead of closing it; the colleague wakes with "handed over by" and closes it with their…

      View evidence: 2.2.1 (opens in a new tab)

    2. 2.2.0

      GitHub releaseSource verified

      Companies bring their own model key. The claude adapter is now a tool-use loop against the Anthropic Messages API, in the server process, on the company's own API key. The agent gets the five tab tools and a finish tool that carries the result contract, and nothing else: no… Show all

      Companies bring their own model key. The claude adapter is now a tool-use loop against the Anthropic Messages API, in the server process, on the company's own API key. The agent gets the five tab tools and a finish tool that carries the result contract, and nothing else: no files, no shell. Token usage is priced per model into the run's model cost. Overloads and 5xx replies are retried. Keys are checked against the API once, sealed with AES-256-GCM under a master key in .key with the company id as additional authenticated data, hinted by their last four characters, and never…

      View evidence: 2.2.0 (opens in a new tab)

    3. 2.1.0

      GitHub releaseSource verified

      A company of agents with tab as the money layer: tab company and the dashboard at Company: a mission, a budget, agents with roles, and tickets. Every run gets its own mandate signed by the company's owner key, capped at the smallest of the company's remaining budget, the agent's… Show all

      A company of agents with tab as the money layer: tab company and the dashboard at https://app.paidwithtab.com. Company: a mission, a budget, agents with roles, and tickets. Every run gets its own mandate signed by the company's owner key, capped at the smallest of the company's remaining budget, the agent's per-run budget and the ticket's cap. What a run spent is what the gateways booked against that mandate, attributed to the run, the ticket and the company. Warns at 80 percent, pauses at 100. A ticket closes only with evidence. Hire, budget, approve, pause and publish are board actions…

      View evidence: 2.1.0 (opens in a new tab)

  3. Code changes, week of 2026-10-12 – 2026-10-18 · 10 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in paidwithtab/tab.

    How HEY read this week

    This week HEY looked inside 1 of 10 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-10-12 – 2026-10-18 · 10 commits (opens in a new tab)

  4. 0.4.2

    GitHub releaseSource verified

    Catalog: 40 live routes across 23 services on the public gateways, between $0.001 and $0.02 a call. Sixteen new services front keyless public APIs: Open-Meteo geocoding, air quality and marine, arXiv, Hacker News, Open Library, Wikidata, Nominatim, Crossref, PubMed, USGS… Show all

    Catalog: 40 live routes across 23 services on the public gateways, between $0.001 and $0.02 a call. Sixteen new services front keyless public APIs: Open-Meteo geocoding, air quality and marine, arXiv, Hacker News, Open Library, Wikidata, Nominatim, Crossref, PubMed, USGS earthquakes, Stack Exchange, CoinGecko, GitHub and OpenAlex. Tavily extraction and Deepgram text to speech join the keyed services. Serper, Exa, Firecrawl, Brave, Mathpix and fal.ai are in the specs behind requires and go live when their key is set. Every live route was exercised with a paid call. Gateway: tab serve…

    View evidence: 0.4.2 (opens in a new tab)

  5. Code changes, week of 2026-10-05 – 2026-10-11 · 51 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in paidwithtab/tab.

    How HEY read this week

    This week HEY looked inside 3 of 51 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 51 commits (opens in a new tab)

  6. 2 releases in paidwithtab/tab on 11 Oct

    GitHub release

    Show all 2 releases

    1. 0.4.1

      GitHub releaseSource verified

      Gateway: evm.rpc may be a comma-separated list; the gateway fails over across endpoints on connection errors, timeouts and HTTP refusals, and stays on the one that answered. Chain answers such as reverts are never retried elsewhere. Specs: a service may list the environment… Show all

      Gateway: evm.rpc may be a comma-separated list; the gateway fails over across endpoints on connection errors, timeouts and HTTP refusals, and stays on the one that answered. Chain answers such as reverts are never retried elsewhere. Specs: a service may list the environment variables it needs in requires. A service whose variable is unset is skipped and logged at start instead of being listed broken. The public specs add web search (Tavily), translation (DeepL) and speech to text (Deepgram) behind provider keys. Package: an exports map, so import { TabClient, tabFetch, receiptOf } from…

      View evidence: 0.4.1 (opens in a new tab)

    2. 0.4.0

      GitHub releaseSource verified

      tab 0.4.0 on npm: npx paidwithtab init gives an agent keys, a mandate, starter credits and the Claude Code line in one command. Public gateways: pay.paidwithtab.com (ledger rail, starter credits), testnet.paidwithtab.com (test USDC on Robinhood Chain testnet) and… Show all

      tab 0.4.0 on npm: npx paidwithtab init gives an agent keys, a mandate, starter credits and the Claude Code line in one command. Public gateways: pay.paidwithtab.com (ledger rail, starter credits), testnet.paidwithtab.com (test USDC on Robinhood Chain testnet) and mainnet.paidwithtab.com (USDG on Robinhood Chain mainnet), all listed at paidwithtab.com/catalog with live receipts. The mainnet gateway settled its first payment on 2026-10-11: https://robinhoodchain.blockscout.com/tx/0xed23…733d

      View evidence: 0.4.0 (opens in a new tab)

  7. Code changes, week of 2026-09-07 – 2026-09-13 · 15 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in paidwithtab/tab.

    How HEY read this week

    This week HEY looked inside 1 of 15 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · 15 commits (opens in a new tab)

What changed

18 changes on HEY’s record for tab: 10 releases · 1 verification change · 1 official source change · 2 build pace changes · 4 other changes in 1 more kind.

All 18 changes for tab →

The full change record holds 5 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 8 of the 10 research questions that apply.

8 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 1h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 5d ago.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 5h ago.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesMeasuredRead 4d ago.

Code and packages

  • Repository detailsMeasuredRead 13h ago.
  • Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources