Saas Pricing
by agent-research-api.onrender.com in Markets & finance
ResearchPi: Check current SaaS headline plan prices, listed features and observed changes for Linear, Supabase, Firecrawl or Clerk. Source URL, retrieval time, missing currency/terms and annual billing are explicit. Optional compare_to snapshot ID; first observation creates a baseline. No complete historical coverage, usage-cost estimate or checkout quote. Failed extraction is not settled. Supported products: GET /pricing-products.
https://agent-research-api.onrender.com/v1/saas-pricing- Price
- $0.02
- per call in USDC
- Uptime
- 45.8%
- last 30 days
- Response time
- 264 ms
- 1.1 s slowest 5%
- Last check
- Failed
- 3 days ago, next any minute now
Reliability
Latest check failed 3 days ago: Expected HTTP 402, got 503
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://agent-research-api.onrender.com/v1/saas-pricing
Each call costs $0.02 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://agent-research-api.onrender.com/v1/saas-pricing
content-type: application/json
{
"product": "linear"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
compare_to | string (uuid) | No | |
product | string | Yes | One of: linear, supabase, firecrawl, clerk. |
Example response
The provider's example. We can't check it without paying.
Example response, 61 lines
{
"billing": {
"amount_usdc": 0.02,
"mode": "production",
"status": "settled"
},
"cache_age_seconds": 0,
"conflicts": [],
"data": {
"comparison": {
"changes": [],
"previous_retrieved_at": null,
"previous_snapshot_id": null,
"status": "baseline_created"
},
"content_hash": "illustrative",
"coverage": "reviewed_headline_plans_only",
"history_scope": "observations_by_this_service; not a complete price history",
"language": "en",
"parser_version": "1",
"plans": [
{
"amount": 0,
"billing_commitment": "unknown",
"currency": null,
"currency_symbol": "$",
"evidence_quote": "Free $0 Free for everyone Unlimited members",
"features": [
"Unlimited members"
],
"name": "Free",
"price_kind": "free",
"price_period": null,
"retrieved_at": "2026-09-20T00:00:00Z",
"source_url": "https://linear.app/pricing",
"unit": null
}
],
"product": "linear",
"retrieved_at": "2026-09-20T00:00:00Z",
"snapshot_id": "11111111-1111-4111-8111-111111111111",
"source_url": "https://linear.app/pricing"
},
"missing_fields": [
"Free.currency",
"Free.unit",
"Free.price_period"
],
"request_id": "example-pricing-not-a-live-transaction",
"retrieved_at": "2026-09-20T00:00:00Z",
"schema_version": "1.0",
"sources": [
{
"retrieved_at": "2026-09-20T00:00:00Z",
"url": "https://linear.app/pricing"
}
],
"warnings": [
"Illustrative excerpt, not a live price quote or transaction."
]
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.02.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://agent-research-api.onrender.com/v1/saas-pricing' \
-H 'content-type: application/json' \
--data-raw '{"product":"linear"}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://agent-research-api.onrender.com/v1/saas-pricing' \
-H 'content-type: application/json' \
--data-raw '{"product":"linear"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fagent-research-api.onrender.com%2Fv1%2Fsaas-pricing&method=POST
const res = await pay("https://agent-research-api.onrender.com/v1/saas-pricing", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"product": "linear"
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://agent-research-api.onrender.com/v1/saas-pricing",
json={
"product": "linear",
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 days ago | Expected HTTP 402, got 503 | 503 | 234 ms | - |
| 3 days ago | Expected HTTP 402, got 503 | 503 | 333 ms | - |
| 3 days ago | Expected HTTP 402, got 503 | 503 | 256 ms | - |
| 4 days ago | Expected HTTP 402, got 503 | 503 | 247 ms | - |
| 4 days ago | Expected HTTP 402, got 503 | 503 | 280 ms | - |
Show 10 older checks
| 4 days ago | Expected HTTP 402, got 503 | 503 | 252 ms | - |
| 4 days ago | Expected HTTP 402, got 503 | 503 | 662 ms | - |
| 4 days ago | Expected HTTP 402, got 503 | 503 | 669 ms | - |
| 5 days ago | Expected HTTP 402, got 503 | 503 | 674 ms | - |
| 5 days ago | Expected HTTP 402, got 503 | 503 | 696 ms | - |
| 5 days ago | Expected HTTP 402, got 503 | 503 | 238 ms | - |
| 5 days ago | Expected HTTP 402, got 503 | 503 | 285 ms | - |
| 5 days ago | Expected HTTP 402, got 503 | 503 | 236 ms | - |
| 5 days ago | Passed | 402 | 789 ms | $0.02 |
| 5 days ago | Passed | 402 | 230 ms | $0.02 |