TinyFish
API Review

We tested seven TinyFish products on real company lookups, public browser tasks and controlled page changes. Finding official sources worked better than turning them into an accurate pricing table.

Tested Nov 17–18, 2026API pilotOne account

Results at a glance

Each row has its own unit and sample. Monitor rows distinguish change judgments, uninterrupted checks and post-Resume checks. The post-Resume row covers two instances. Browser results cover the pagination task.

Run usage and billing status
Product Observed result Usage recorded for the tested runs
TinySearch Found a usable official product landing and pricing source within five returned links for all 12 named companies. First link passed for 3/12 product and 5/12 pricing queries. $0 in AgentRouter receipts
TinyFetch Returned 190/192 readable pages and matched 279/343 details for supplied URLs. $0 in the November 15 study
TinyAgent Returned all four bookstore fields and matched the reference outputs on two dynamic pages. $0.144 pending for the bookstore; $0.08 and $0.128 shown for the two Playground runs
TinyBrowser Retrieved all four bookstore fields after a retry and all five JavaScript pagination fields on a separate run. About $0.002 pending across the two bookstore sessions; $0.006 shown for the pagination session
TinyMonitor Correctly judged two edits. In the November 18 audit, matched active controls completed 10/10 and 5/5 checks while REST-resumed instances completed 0/10 and 0/5. $0.015 pending for an initial baseline and two manual checks
TinyResearch Answered four verifiable questions. Its 734-word report exceeded the 500-word limit. $2.00 pending for one Deep run
TinySet Returned 12 rows, covering 6/12 requested companies. Passed 26/72 field checks; 2/12 requested rows passed all six. $1.20 pending for this 12-row run; earlier workflow pilot $0.30 pending

Search and TinySet include the November 18 real-company study. Other recorded amounts cover the original runs and exclude the November 18 Monitor replication. TinySet Wallet showed 12 rows at $0.10 per row, totaling $1.20 pending. These are usage records, not a total invoice for the review. TinyFish publishes rates per Agent step, Browser minute, Monitor check, Research run and TinySet row. TinyFish pricing

TinyMonitor

Ordinary recurring schedules reproduced the Resume gapNovember 18 · More than ten minutes after REST Resume · One account
ScheduleBefore Pause
Resumed instance
Active control
Same post-Resume slots
After Resume
Resumed instance
Every minute3/310/100/10
Every two minutes2/25/50/5

Source fetches and webhooks agreed in every cell. Both instances reported active. Manual runs after the observation window read $31. Audit data

Every scheduled slot in the longer replicationNovember 18 · 10:48–11:02 a.m. Pacific · Ordinary recurring cron
Observed×Unobserved after ResumeⅡPaused·No check due
Minute columns from 10:48 a.m. to 11:02 a.m. on November 18.
Before PausePausedAfter Resume
10–11 a.m.484950515253545556575859000102
Control · 1 minControl · 1 min, 10:48 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 1 min, 10:49 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 1 min, 10:50 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 1 min, 10:51 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 1 min, 10:52 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 1 min, 10:53 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 1 min, 10:54 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 1 min, 10:55 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 1 min, 10:56 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 1 min, 10:57 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 1 min, 10:58 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 1 min, 10:59 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 1 min, 11:00 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 1 min, 11:01 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 1 min, 11:02 AM Pacific. 1 source fetch; 1 webhook in this due minute.
REST Resume · 1 minREST Resume · 1 min, 10:48 AM Pacific. 1 source fetch; 1 webhook in this due minute.REST Resume · 1 min, 10:49 AM Pacific. 1 source fetch; 1 webhook in this due minute.REST Resume · 1 min, 10:50 AM Pacific. 1 source fetch; 1 webhook in this due minute.REST Resume · 1 min, 10:51 AM Pacific. Paused.REST Resume · 1 min, 10:52 AM Pacific. Paused.REST Resume · 1 min, 10:53 AM Pacific. 0 source fetch; 0 webhook in this due minute.REST Resume · 1 min, 10:54 AM Pacific. 0 source fetch; 0 webhook in this due minute.REST Resume · 1 min, 10:55 AM Pacific. 0 source fetch; 0 webhook in this due minute.REST Resume · 1 min, 10:56 AM Pacific. 0 source fetch; 0 webhook in this due minute.REST Resume · 1 min, 10:57 AM Pacific. 0 source fetch; 0 webhook in this due minute.REST Resume · 1 min, 10:58 AM Pacific. 0 source fetch; 0 webhook in this due minute.REST Resume · 1 min, 10:59 AM Pacific. 0 source fetch; 0 webhook in this due minute.REST Resume · 1 min, 11:00 AM Pacific. 0 source fetch; 0 webhook in this due minute.REST Resume · 1 min, 11:01 AM Pacific. 0 source fetch; 0 webhook in this due minute.REST Resume · 1 min, 11:02 AM Pacific. 0 source fetch; 0 webhook in this due minute.
Control · 2 minControl · 2 min, 10:48 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 2 min, 10:49 AM Pacific. No check due.Control · 2 min, 10:50 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 2 min, 10:51 AM Pacific. No check due.Control · 2 min, 10:52 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 2 min, 10:53 AM Pacific. No check due.Control · 2 min, 10:54 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 2 min, 10:55 AM Pacific. No check due.Control · 2 min, 10:56 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 2 min, 10:57 AM Pacific. No check due.Control · 2 min, 10:58 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 2 min, 10:59 AM Pacific. No check due.Control · 2 min, 11:00 AM Pacific. 1 source fetch; 1 webhook in this due minute.Control · 2 min, 11:01 AM Pacific. No check due.Control · 2 min, 11:02 AM Pacific. 1 source fetch; 1 webhook in this due minute.
REST Resume · 2 minREST Resume · 2 min, 10:48 AM Pacific. 1 source fetch; 1 webhook in this due minute.REST Resume · 2 min, 10:49 AM Pacific. No check due.REST Resume · 2 min, 10:50 AM Pacific. 1 source fetch; 1 webhook in this due minute.REST Resume · 2 min, 10:51 AM Pacific. No check due.REST Resume · 2 min, 10:52 AM Pacific. Paused.REST Resume · 2 min, 10:53 AM Pacific. No check due.REST Resume · 2 min, 10:54 AM Pacific. 0 source fetch; 0 webhook in this due minute.REST Resume · 2 min, 10:55 AM Pacific. No check due.REST Resume · 2 min, 10:56 AM Pacific. 0 source fetch; 0 webhook in this due minute.REST Resume · 2 min, 10:57 AM Pacific. No check due.REST Resume · 2 min, 10:58 AM Pacific. 0 source fetch; 0 webhook in this due minute.REST Resume · 2 min, 10:59 AM Pacific. No check due.REST Resume · 2 min, 11:00 AM Pacific. 0 source fetch; 0 webhook in this due minute.REST Resume · 2 min, 11:01 AM Pacific. No check due.REST Resume · 2 min, 11:02 AM Pacific. 0 source fetch; 0 webhook in this due minute.

Every minute was observed in full before manual calls. After Resume, the matched active controls completed 10/10 and 5/5 checks. The resumed instances completed 0/10 and 0/5.

In the first controlled run, TinyMonitor correctly ignored an announcement edit and marked the Pro price increase from $20 to $25 relevant. Four scheduled callbacks, including two unchanged checks, arrived 2.9–8.2 seconds into their respective minute slots. This tested change judgment and delivery while the monitor stayed active. Original change events

Source-fetch and webhook counts agreed in each cell. Both Resume calls returned HTTP 200, and a separate GET confirmed both instances active with no reported error. The fixture logged no post-Resume source requests from either instance before the manual calls. Dashboard All checks stayed at six and four baseline-plus-pre-pause entries. Two subsequent manual calls returned HTTP 201 and read the current $31 price, adding one history entry each. Independent source log, webhook receipts and Dashboard checks

These runs support a reproducible gap in scheduled execution after Resume for this account and tested configuration. The 0/12 figure was a scoped interruption test. It cannot serve as an overall Monitor success rate. We have not established the internal cause or measured prevalence across accounts. All four new test instances were paused after the audit. Full audit evidence

Exact method and the earlier comparison

On November 18 we created four fresh Page Monitors under the same account, using ordinary recurring cron expressions * * * * * and */2 * * * *. For each cadence one stayed active and one received status-only REST updates to pause and resume. The observation window ran from 10:48 to 11:03 a.m. Pacific. We paused at 10:50:20, resumed at 10:52:20, and waited until after 11:03 before making manual calls. Every expected minute was observed in full. Plan, request bodies and timestamps · Official lifecycle contract

The November 17 comparison had shown the same gap through Dashboard and REST Resume, at both cadences, using calendar-restricted cron expressions. Its 0/12 figure counted four instances’ first three expected execution times. In the two-minute cases, we made the manual call about 45 seconds into the third due minute. That limited the original observation of that slot. The November 18 repeat used unrestricted recurring schedules and a longer untouched window to address that limitation. Original comparison · Independent recount and replication

November 17 · Four instances had no observed post-Resume requestsScheduled source fetches and webhook counts matched in these comparison cells.
Continuously active controls versus the first three due checks after Resume
ScheduleAlways active
Full window
Dashboard Resume
First three due times
REST Resume
First three due times
Every minute11/110/30/3
Every two minutes6/60/30/3

One account, six fresh monitors, one fixed observation window. All four resumed instances still read $31 on manual runs.

TinyFetch

A readable page still needs a field checkNovember 15 · Exact URLs supplied through AgentRouter
Pages with readable text190/192
Expected details matched279/343
Prices with billing units46/59
Customer quotes105/127

Firecrawl pricing page

9/9

Expected prices matched

Tiptap pricing page

0/6

Readable text, six prices missing

In the November 15 study, we supplied 192 exact URLs and checked page text against 343 details. TinyFetch found 46 of 59 prices and 105 of 127 customer quotes. It matched all nine expected prices on Firecrawl’s pricing page and zero of six on Tiptap’s, even though both responses contained readable text. The median run took 1.64 seconds, with a 9.2-second P95. When a workflow uses extracted prices, verify the amounts and billing units against the source. TinyFetch task review · Website benchmark methodology

TinyAgent and TinyBrowser

Three public browser workflowsOutputs checked against the fixture values
TaskTinyAgent
Natural-language goal
TinyBrowser
Evaluator-written script
Bookstore product4/4 fields4/4 fields
JavaScript pagination5/5 fields5/5 fields
AJAX year change2/2 year rowsNot tested

The successful bookstore Browser run followed a client retry. Browser script timings exclude provisioning and script authoring.

Both tools retrieved the requested title, price, stock line and URL for It’s Only the Himalayas from a public bookstore fixture. TinyAgent ran for 54 seconds after we removed the unsupported root-level additionalProperties keyword from the output schema. The first TinyBrowser client attempt timed out after 50 seconds. On retry we narrowed the link selector and changed how the client exited on errors. The second attempt returned all four fields in 2.64 seconds, including its CDP connection. The cause of the timeout remains unknown. Bookstore fixture · Run outputs

For JavaScript pagination, both returned the right page URL, card count, first two authors and visible Previous link. TinyAgent followed a natural-language goal. TinyBrowser ran our Playwright script in 2.33 seconds including its CDP connection. That timing excludes provisioning and script authoring. In another TinyAgent run, it switched an AJAX awards table from 2014 to 2015, waited for the new rows and returned the correct winners with their award and nomination counts. We tested public, read-only workflows. Pagination fixture · AJAX fixture · Outputs and reference values

TinyResearch and TinySet

Four answers checked, one length limit exceededTinyResearch Deep · One Bing AI Performance brief
  • ✓What total citations count
  • ✓What grounding queries represent
  • ✓How queries map to cited pages
  • ✓How the report relates to rankings
Report length734 words
500-word cap

234 words over the requested limit · approximately 47% over

We asked TinyResearch Deep for a brief explaining Bing Webmaster Tools’ AI Performance report. Four answers about citation counts, grounding queries, which pages a query cited and traditional search rankings agreed with Microsoft's documentation. The report finished in 2 minutes 19 seconds and ran to approximately 734 words on a 500-word request. Microsoft's reference · Research run and citation checks

A filled table lost half the requested companiesTinySet · One automatically planned run · Same 12-company sample
6/12Requested companies returned12 rows generated in total
2/12Requested rows completeAll six checks passed
26/72Field checks passedMissing companies score zero

Company coverage

LinearNotionLoomFigmaFirecrawlResendBrowserbaseExaTiptapRetoolElevenLabsGlean

Added outside the requested listAtlassian · Dropbox · Slack · Stripe · Vercel · Zoom

Each check uses the 12 requested companies

Product page6/12
Pricing page6/12
Entry plan / rate5/12
Amount + currency2/12
Billing basis5/12
Source supports price tuple2/12

Company names were supplied and earned no field point. A correct billing-unit field could pass independently of the amount. Source support required the whole returned plan, amount and billing conditions to agree.

The returned price, beside the checked official priceRegular month-to-month billing · USD · Captured November 18

These are the provider's original claims. The reference column is our independent check. Each price links to its source; the missing companies remain visible.

CompanyTinySet returnedOfficial reference checkedChecks
LinearBusiness · $16per user per month, billed monthlyReturned source ↗Basic · $12per user / month · monthly billingOfficial reference ↗3/6Wrong amount + entry plan
NotionPlus · $10per month per memberReturned source ↗Plus · $12per member / month · monthly billingOfficial reference ↗3/6Annual equivalent; commitment missing
LoomNo row returnedBusiness · $18per user / month · monthly billingOfficial reference ↗0/6Missing requested company
FigmaProfessional · $16per month per Full seat, billed monthlyReturned source ↗Professional · $20per Full seat / month · monthly billingOfficial reference ↗4/6Annual price labeled monthly
FirecrawlNo row returnedHobby · $19per month · monthly billingOfficial reference ↗0/6Missing requested company
ResendNo row returnedPro · $20per month · monthly billingOfficial reference ↗0/6Missing requested company
BrowserbaseNo row returnedDeveloper · $20per month · monthly billingOfficial reference ↗0/6Missing requested company
ExaLite Search · $4per 1,000 requests, pay-as-you-go, up to 10 resultsReturned source ↗Lite Search · $4per 1,000 requests · pay as you goOfficial reference ↗6/6All six checks passed
TiptapNo row returnedStart · $49per month · hosted platform · monthly billingOfficial reference ↗0/6Missing requested company
RetoolTeam · $10per month per builder, monthly billingReturned source ↗Team · $12per builder / month · monthly billingOfficial reference ↗4/6Annual price labeled monthly
ElevenLabsStarter · $6per month, month-to-monthReturned source ↗Starter · $6per month · after promotionOfficial reference ↗6/6All six checks passed
GleanNo row returnedNo numeric base-seat rate verifiedChecked product and sales referencesOfficial reference ↗0/6Missing requested company

Monthly toggles were checked before testing. Exa uses a request unit; ElevenLabs excludes the temporary $1 first month. Glean's reference does not establish the absence of a price everywhere. Download the sourced comparison CSV ↓

Exact TinySet prompt, field checks and run limitations

We sent the same company list and product hints directly to TinySet. It did not receive TinySearch's results, reference URL paths or expected prices. The API generated its own ten-column spec. No row was repaired, replaced or retried before scoring.

  1. Product page: official and explains the named product.
  2. Pricing page: official rates or a direct sales enquiry for the unpublished case.
  3. Plan or rate: the requested entry nonfree standard plan.
  4. Amount and currency: regular monthly USD amount, or Exa's stated request unit.
  5. Billing basis: period, role or request unit and commitment are explicit.
  6. Source support: the cited page supports the complete returned price tuple.

Each requested company has six checks. Missing companies receive zero; unrelated replacements receive no credit. Company names earn no field point. Nulls pass only where unavailable in the verified references. The 72 checks are six conditions on 12 companies, not 72 independent samples.

Create exactly one row for each of the 12 real companies listed below, for the named product. Research their current public official websites. Find an official product landing page and its official pricing page, then record a supported regular paid starting price. The purpose is a vendor-comparison table that a buyer can verify from source links.

Companies, target products and official root domains:
- Linear | Linear project management | linear.app
- Notion | Notion workspace | notion.com
- Loom | Loom screen recorder | loom.com
- Figma | Figma Design full seat | figma.com
- Firecrawl | Firecrawl Scrape | firecrawl.dev
- Resend | Resend transactional Email API | resend.com
- Browserbase | Browserbase cloud browsers | browserbase.com
- Exa | Exa Lite Search API | exa.ai
- Tiptap | Tiptap hosted platform with editor | tiptap.dev
- Retool | Retool Apps builder seat | retool.com
- ElevenLabs | ElevenCreative Text to Speech | elevenlabs.io
- Glean | Glean AI Assistant | glean.com

Return exactly these 10 columns, with these names:
1. company (string, primary key) - use the listed company name.
2. product_url (url) - official landing page explaining the named product.
3. pricing_url (url) - official price/rate page. When the checked official site provides only sales enquiries and no published rate, return the direct sales contact/demo page.
4. plan_or_rate (string) - the lowest nonfree standard paid plan for that product, or the name of its pay-as-you-go rate. Null when no plan is publicly specified.
5. price_amount (number) - numeric USD amount for the regular MONTH-TO-MONTH price, not annual billing. For a pay-as-you-go API quote the amount per stated request unit. Null if no numeric price is published.
6. currency (string) - currency of the published amount. Null with an unpublished amount.
7. billing_basis (string) - include the time period and role/seat or request unit, and any commitment. Use Full seat for Figma Design, builder for Retool Apps, and Lite Search for Exa. For no published amount, state that a quote is needed.
8. pricing_status (string) - published, contact_sales, or unknown.
9. price_source_url (url) - the official page supporting this particular plan/rate, amount and billing basis. May match pricing_url.
10. price_evidence (string) - a short supporting excerpt from that source, at most 18 words.

Use regular recurring prices. Exclude zero-price/free plans, free trials, temporary first-month discounts, add-ons and overage charges when choosing the entry plan. For ElevenCreative use its regular price AFTER any first-month promotion. For Resend use transactional Email API plans, not Marketing or add-ons. For Tiptap use the paid hosted platform, not the free open-source Editor. Exa Lite Search is usage-priced, so preserve the request-count unit.

Use current official evidence for every filled price. If a value cannot be verified, leave it null or unknown instead of guessing. Use only the 12 listed companies. Do not add other companies or duplicates. The root domains identify the companies, and you must discover the product and pricing paths yourself.

Use the dataset name SOTA2 real-company product and price study 2026-11-18 6pk4.

One automatically planned run, one account. It finished about 48 seconds after creation. Wallet showed $1.20 pending for 12 rows at $0.10 each. A seeded-row or alternative-spec recovery was not tested. The evidence excerpt for Exa exceeded the 18-word request; we record that formatting issue separately from the six scored conditions.

Untouched rows, per-field decisions and billing record ↓

For TinySet, the job was a buyer-verifiable vendor table: one row for each of the same 12 companies, with product and pricing URLs, entry paid plan, amount, currency, billing basis and a supporting official source. The prompt required regular month-to-month pricing, excluded free tiers and temporary promotions, specified Figma Full seats and Retool builders, and preserved Exa's request unit. Company names and root domains were supplied; answer paths and prices were withheld. This was an independent TinySet run on the same sample. It did not receive TinySearch's returned links. Exact request and untouched returned rows

The direct API automatically generated a ten-column spec and returned 12 rows. Only six belonged to the requested companies. Loom, Firecrawl, Resend, Browserbase, Tiptap and Glean were missing; Slack, Zoom, Atlassian, Dropbox, Vercel and Stripe appeared instead. We confirmed both the original prompt and the same returned rows in TinyFish's dashboard. There were no duplicate company names and no manual row repairs. Request, API rows and coverage

Six checks applied to every requested row: correct product page, pricing page, plan, amount and currency, billing basis, and source support for the returned price tuple. Missing requested companies earned zero; unrelated replacements earned no credit. The run passed 26/72 checks. Exa and ElevenLabs were the only requested rows passing all six, for 2/12 complete rows. A billing-unit point could pass independently of the amount; the source-support point required the plan, amount and billing conditions to agree together. Per-field decisions and sourced CSV

Figma and Retool illustrate the pricing failure. TinySet labeled $16 per Full seat and $10 per builder as monthly billing. Those were annual-billing equivalents. Before the run, we switched the official pages to monthly and verified $20 and $12 respectively. Notion returned the $10 annual equivalent instead of $12 monthly and omitted the commitment. Linear returned Business at the $16 annual equivalent, although the task asked for the lowest paid plan, Basic at $12 monthly. Links to official pricing pages did not support those claimed tuples. Figma pricing · Retool pricing · Notion pricing · Linear pricing

Exa preserved Lite Search at $4 per 1,000 requests. ElevenLabs selected the regular $6 Starter rate after its $1 first-month offer. The server reported completion about 48 seconds after dataset creation; the next status poll confirmed ready with all rows readable. Wallet recorded $1.20 pending for 12 rows at $0.10 each. This was one automatically planned run in one account. It establishes observed coverage and price errors for this request; the internal cause and performance with seeded rows or another spec remain untested. The earlier three-domain workflow check remains available as historical evidence. Real-company run and scoring · Exa pricing · ElevenLabs pricing · Earlier workflow pilot

What we tested

This API pilot covers seven products on November 17–18, with Fetch results reused from November 15. We used AgentRouter for Search and the earlier Fetch study, TinyFish's direct APIs for the other five products, and its dashboard and Playground for follow-up checks. Search and TinySet received the same purposive 12-company sample on November 18. Four subscription cases were Linear, Notion, Loom and Figma; four API cases were Firecrawl, Resend, Browserbase and Exa; four pricing cases were Tiptap's hosted platform, Retool builder seats, ElevenLabs promotions and Glean sales enquiries. These strata were selected for different price-reading conditions, without a claim that every company fits only one category. Frozen dataset manifest

We fixed the companies, references, query templates and scoring rules at 19:38:45 UTC before the first new Search run at 19:38:59. Reference prices came from official pages; monthly toggles were checked before testing. Additional official pages could qualify after independent content verification, with their rulings saved separately. Prices represent the November 18 observation, exclude taxes and may change. We checked each requested company's identity, not just output row count. The 72 TinySet checks measure six conditions per requested company, not 72 independent samples. Inputs, reference provenance, receipts and all decisions

The 12 companies form a small, hand-selected workflow study. Search was given the correct domains. TinySet had one automatically planned run. These results do not measure open-ended company discovery, repeated-run reliability, or a combined Search-to-TinySet pipeline. The broader review also did not test a combined Search-to-Fetch workflow, topic monitoring, email delivery, authenticated browser workflows, vault or saved browser profiles, enterprise access, or sustained workloads. The browser tasks were public and read-only; the Monitor replication used a synthetic controlled page under one account. Original test evidence · Monitor audit

Test data

Download the exact inputs, returned values and scoring. The files are public and remain available independently of a TinyFish login. Official reference pages can change after the November 18 observation.

TinyFish product profile · TinyFish company · TinyFetch Task Review