Developer portal
Build on the public layer.
Use the same jobs, news, events, and glossary data that powers Hashtag Web3. Start with a public endpoint, inspect the schema, and move to authenticated surfaces only when you need them.
Public by default
Read endpoints require no key and support CORS for browser integrations.
Agent-ready
Use discovery files, MCP, and the auth guide to make integrations legible to tools.
Stable surfaces
Canonical JSON APIs and feed endpoints are designed for practical consumption.
REST API
Four useful starting points.
All standard read endpoints are unauthenticated. Add query parameters for search, limits, offsets, and filters.
Quickstart
One request, useful data.
Start with standard HTTP. The API returns JSON and includes pagination metadata for production clients.
curl -X GET \
"https://hashtagweb3.com/api/jobs?search=Solidity&limit=5" \
-H "Accept: application/json"Machine-readable files
Discovery without the scavenger hunt.
Authentication
Read openly. Authenticate when needed.
Public read endpoints are free to query. Agents and partners that need elevated limits or write operations can use the documented registration and bearer-token flow.
- Public read endpoints need no key.
- Agent registration returns a scoped token.
- CORS is enabled for browser integrations.