Best Web3.career API in 2026
Best Web3.career API in 2026 by listed price: 9 SandBase endpoints, each $0.01. Official free access covers one listings endpoint, not companies or salaries.
A job listing, a company directory, and a salary table can share a careers site and still be three products. On the 21 Nov 2026 catalog check (Asia/Shanghai), Web3.career on SandBase listed 9 endpoints, all $0.01 per call. The HTML title was “Web3.career APIs: Crypto Jobs, Companies and Salaries | SandBase.” /apis/web3 and /apis/web3career returned HTTP 404. The call vendor is web3-career. The official landing, title “Web3 Jobs API,” describes free access to one listings endpoint. That product does not cover SandBase company, salary, or intelligence-report cards. This is not a jobs umbrella. Compensation research on another catalog is Best Levels.fyi API in 2026. Official docs opened here have no dollar rate card. Accuracy and latency against other vendors stay Unknown, because this article did not run that comparison.
Key takeaway
- On 21 Nov 2026 the SandBase Web3.career hub at
/apis/web3-careerlisted 9 endpoints. Every card was $0.01 per call.- Job Search, Job Detail, Salaries, and Companies did not show a “100 free calls / day” row. Do not treat this hub as free-quota eligible.
- Official access is described as free for a single listings endpoint. It does not cover companies, salaries, or the intelligence report. No dollar rate card was on the opened docs.
- One thousand calls at $0.01 are $10.00 only as list-price math, not a bill. No ceiling is stated.
- Call
POST https://api.sandbase.ai/v1/api/web3-career/{endpoint}with a Bearer key. The captured cards show Async JSON. PollGET https://api.sandbase.ai/v1/run/{id}. Do not POST/v1/runto start.
What a Web3.career API means in 2026
Stop before you treat the official free listings endpoint as the whole hub. Salaries and companies are SandBase cards. The official landing does not price them.
The first official product is the Web3 Jobs API. On 21 Nov 2026 web3.career/web3-jobs-api, title “Web3 Jobs API,” said “Free access to 103,557 Web3 job listings via a single API endpoint.” Filters cover technology, role, and location or remote. A call returns 1 to 100 listings, with optional descriptions. The docs, title “API Overview | Web3.Career Jobs API | Bondex,” set the base URL at https://web3.career/api/v1, GET, a token query parameter, JSON or /v1.xml. Rate limits return 429. The maximum is 100. There is no cursor pagination. apply_url requires a follow link. No dollar rate card sat on that page. The official product does not 1:1 cover SandBase companies, salaries, or the intelligence report.
The second purchase is a separate unofficial vendor account for job or salary records. This article does not name those vendors or borrow anyone else’s accuracy scores. This page does not open a jobs-board series.
The third is the SandBase hub. SandBase is not Web3.career. A catalog row does not grant the official listings token. Official Web3.career terms still apply, including the attribution rule on apply_url when that official endpoint is the one in use.
Web3.career endpoints you can call on SandBase today
The wider data API index listed 2,247 endpoints from 182 providers on the same check. On this hub the listed price does not vary. The official coverage does.
| Card | List price, 21 Nov 2026 | Call | What the card describes | Async | Free allowance |
|---|---|---|---|---|---|
| Job Search | $0.01 per call | POST /v1/api/web3-career/search-jobs | Crypto jobs by keyword | Async JSON | No visible row |
| Job Detail | $0.01 per call | POST /v1/api/web3-career/job-detail | Full listing from a URL | Async JSON | No visible row |
| Salaries | $0.01 per call | POST /v1/api/web3-career/web3-salaries | Average pay by crypto role | Async JSON | No visible row |
| Companies | $0.01 per call | POST /v1/api/web3-career/web3-companies | Crypto companies hiring | Async JSON | No visible row |
The other five cards on the hub Markdown, at the same $0.01, were Company Jobs (company-jobs), Intelligence Report (intelligence-report), Job Listings (job-listings), Jobs By Tag (jobs-by-tag), and Remote Jobs (remote-jobs). Salaries, companies, and the intelligence report are SandBase cards. The official free listings endpoint does not cover them. All 9 cards share one listed price. The vendor segment is web3-career on every POST.
None of the four cards above showed “100 free calls / day — First 100 calls per day free (shared per organization) · Resets at 00:00 UTC. Pay per call after that.” Do not describe these cards, or the hub, as free-quota eligible. The official free listings endpoint is not that row.
![]()
SandBase Web3.career hub, logged out, 21 Nov 2026 (Asia/Shanghai). HTML title: “Web3.career APIs: Crypto Jobs, Companies and Salaries | SandBase.” Path /apis/web3-career. Nine endpoints at $0.01. Official free access covers one listings endpoint and was not captured as a dollar rate card.
![]()
Web3.career Job Search card, logged out, 21 Nov 2026 (Asia/Shanghai). Title: “Web3.career Job Search API: Find Crypto Jobs by Keyword | SandBase.” Listed price $0.01. Async JSON. No 100-free-calls row.
![]()
Web3.career Job Detail card, logged out, 21 Nov 2026 (Asia/Shanghai). Title: “Web3.career Job Detail API: Full Listing from a URL | SandBase.” Listed price $0.01. Async JSON. No 100-free-calls row.
![]()
Web3.career Salaries card, logged out, 21 Nov 2026 (Asia/Shanghai). Title: “Web3.career Salaries API: Average Pay by Crypto Role | SandBase.” Listed price $0.01. A SandBase card, not the official listings API. Official free access does not cover salaries. Async JSON. No 100-free-calls row.
![]()
Web3.career Companies card, logged out, 21 Nov 2026 (Asia/Shanghai). Title: “Web3.career Companies API: Crypto Companies Hiring Now | SandBase.” Listed price $0.01. A SandBase card, not the official listings API. Official free access does not cover companies. Async JSON. No 100-free-calls row.
Official Web3.career listings versus SandBase catalog prices
The rows are different products. The table is not a rank. Latency and accuracy are Unknown in every row.
| Path | What you can call, as checked 21 Nov 2026 | Billing | Free trial or allowance | Docs |
|---|---|---|---|---|
| Official Web3 Jobs API | One listings endpoint. Filters for technology, role, and location or remote. 1 to 100 listings. | No dollar rate card on the opened docs. | Described as free access to that single listings endpoint. Not companies, salaries, or the intelligence report. Not a SandBase quota. | Web3 Jobs API and docs |
| SandBase Web3.career hub | 9 research endpoints, each $0.01, including search, detail, companies, salaries, and an intelligence report. | Pay per call, no subscription. Start ($0), Build (Metered), Scale (Custom). | The captured cards did not show a free-calls row. Eligible data APIs elsewhere share 100 free calls per organization per UTC day. | Live cards plus API passthrough |
| A separate unofficial vendor account | Whatever that vendor lists. Not measured here. | That vendor’s contract. Unknown here. | Unknown here. | That vendor’s own docs |
Free official listings access cannot be copied onto a SandBase salary card. The opened docs did not publish a dollar rate for that official endpoint either.
Best Web3.career API for each need
- Listed SandBase price: $0.01 on all 9 cards. Search, detail, salaries, and companies share that floor.
- Job reads that resemble the official listings product: Job Search, Job Detail, Job Listings, Jobs By Tag, Remote Jobs, and Company Jobs. They are still $0.01 SandBase calls. The official free endpoint is a different contract.
- Companies, Salaries, and Intelligence Report: SandBase cards at $0.01. Official free access does not cover them.
- Confirmed free-quota cards: none of the cards opened here.
- Broader compensation benchmarks are Best Levels.fyi API in 2026. That post is not a jobs umbrella, and neither is this one.
How to call the Web3.career API on SandBase
Data APIs use POST https://api.sandbase.ai/v1/api/{vendor}/{endpoint} with Authorization: Bearer $SANDBASE_API_KEY and a JSON body. Language models use POST /v1/chat/completions. Media models use POST /v1/run. Do not start a data API with POST /v1/run. The passthrough reference is the data-API page. The first API call walkthrough is chat completions only.
Job Search, Job Detail, Salaries, and Companies showed Async JSON on 21 Nov 2026. The POST still starts the call. When status is not completed, poll GET https://api.sandbase.ai/v1/run/{id} until it is. That GET is the poll. Do not POST /v1/run to start. This comparison did not run a paid call. Replace the empty object with the fields on the live Job Search card before you send it. Read outputs[0].data. If that object is missing, fail loudly.
import os
import time
import requests
payload = {} # replace with the fields on the live Web3.career Job Search card before sending
headers = {
"Authorization": f"Bearer {os.environ['SANDBASE_API_KEY']}",
"Content-Type": "application/json",
}
response = requests.post(
"https://api.sandbase.ai/v1/api/web3-career/search-jobs",
headers=headers,
json=payload,
timeout=90,
)
response.raise_for_status()
body = response.json()
# Job Search shows Async JSON. Poll GET /v1/run/{id}. Do not POST /v1/run to start.
run_id = body.get("id")
if body.get("status") != "completed":
if not run_id:
raise RuntimeError(f"SandBase call returned no id: {body.get('status')} {body.get('error')}")
for _ in range(30):
time.sleep(2)
poll = requests.get(
f"https://api.sandbase.ai/v1/run/{run_id}",
headers=headers,
timeout=90,
)
poll.raise_for_status()
body = poll.json()
if body.get("status") == "completed":
break
outputs = body.get("outputs") or []
if body.get("status") != "completed" or not outputs or not isinstance(outputs[0], dict):
raise RuntimeError(f"SandBase call did not complete: {body.get('status')} {body.get('error')}")
data = outputs[0].get("data")Job Detail is /v1/api/web3-career/job-detail. Salaries is /v1/api/web3-career/web3-salaries. Companies is /v1/api/web3-career/web3-companies. Those captured cards use the same poll. The snippet is a client sketch, not a measured latency.
![]()
API passthrough page, logged out, 21 Nov 2026 (Asia/Shanghai). Title: “API Passthrough.” Documents POST /v1/api/{vendor}/{endpoint}. The vendor segment is web3-career. Not the official free listings endpoint.
What the daily allowance does and does not cover
Pricing and Pricing and Usage, checked 21 Nov 2026, give every organization 100 free data API calls per UTC day. The pool is shared across eligible data APIs and all org keys, resets at 00:00 UTC, and does not carry over. Language models, media models, and some pricier data APIs are billed from the first call. A card counts as eligible here only when the live tool card shows the free-calls row. These Web3.career cards did not. The official free listings endpoint is not that row. After the 100th eligible call on tools that do qualify, requests still complete and are billed. A zero balance can still spend remaining allowance. Failed calls are not charged. Catalog browsing is $0. Plans are Start ($0), Build (Metered), and Scale (Custom). Web3.career is absent from the pricing-page sample list, and that list is not a complete roster.
![]()
Pricing page, logged out, 21 Nov 2026 (Asia/Shanghai). Title: “SandBase Pricing: Models, APIs and Usage-Based Billing.” Pay per call. Not the official Web3.career listings page.
![]()
Pricing and Usage guide, logged out, 21 Nov 2026 (Asia/Shanghai). Title: “Pricing and Usage.” Eligible data APIs share 100 free calls per organization per UTC day. These Web3.career cards did not show that row.
One thousand calls at $0.01 are $10.00 only if every call bills at that price. That is list-price math, not an invoice. Do not subtract 100 calls, and do not treat the official free listings endpoint as a credit against a SandBase salary call. This article does not state a ceiling.
When not to use the SandBase Web3.career hub
Stay on the official listings endpoint when the job is that single free listings API, with its token, its 100-item cap, and its attribution rule. A catalog row is not that endpoint. Official Web3.career terms still apply. Stay on Levels.fyi when the job is that catalog’s compensation benchmarks. Stay put when the buying criterion is a published official dollar rate card or a measured accuracy or latency rank. This check did not produce that rank, and the opened docs did not publish a dollar card. This page is not a jobs-board umbrella.
FAQ
What does “Web3.career API” mean in this article?
The 9 SandBase cards on /apis/web3-career, checked 21 Nov 2026. It is not /apis/web3 or /apis/web3career, which returned HTTP 404. It is not only the official free listings endpoint, and it is not a jobs umbrella.
When is the SandBase hub a better fit than the official listings API?
For a public job search, job detail, company list, salary read, or intelligence report billed per call on one key. For the free single listings endpoint, start with the official page. That endpoint does not cover companies, salaries, or the intelligence report.
How much do the SandBase Web3.career endpoints cost?
$0.01 per call on all 9 cards, on the 21 Nov 2026 hub list. One thousand calls are $10.00 as list-price math only. This article does not state a ceiling. The official docs opened here did not publish a dollar rate.
Are the first 100 Web3.career calls free?
Not on the cards opened here. Job Search, Job Detail, Salaries, and Companies did not show the shared 100-calls row. Official free access is one listings endpoint, not this hub. Eligible data APIs elsewhere share 100 free calls per organization per UTC day.
How do official Web3.career prices compare with SandBase?
The official landing describes free access to one listings endpoint and does not publish a dollar rate card on the opened docs. SandBase lists 9 research endpoints at $0.01, including companies, salaries, and an intelligence report. Those extra cards are not the official free endpoint. Latency and accuracy were not measured.
Do official Web3.career terms still apply?
Yes. A catalog price is not the official listings token and does not replace Web3.career’s terms, including attribution on apply_url when that official endpoint is in use.
How do I start a call?
POST https://api.sandbase.ai/v1/api/web3-career/search-jobs (or job-detail, web3-salaries, web3-companies) with a Bearer key. Those cards show Async JSON, so poll GET https://api.sandbase.ai/v1/run/{id} until status is completed. Do not POST /v1/run to start.
Related reading
Compensation benchmarks on another catalog are Best Levels.fyi API in 2026. That post is not a jobs umbrella, and this page does not become one.
Open the Web3.career hub, then Job Search or Salaries beside the passthrough reference. Read pricing and Pricing and Usage, then sign up. Create a key in the Console, or start an agent from the skill file.
Found this useful? Share it