Tech Twitter Developer Portal

Give agents compact, citation-ready evidence about what changed, what launched, what people are arguing about, what is worth reading, and which narratives are emerging across curated tech discourse.

Auth: None
Mode: Read only
Format: JSON

Context API / quickstartGET · /api/agent/context

Quickstart

One request, ranked evidence

GET /api/agent/context

Set kind=auto and pass a natural-language question, or choose a recipe directly. The response contains evidence rows, provenance, metrics, facets, instructions, and canonical citation URLs.

curl --get 'https://www.techtwitter.com/api/agent/context' \
  --data-urlencode 'kind=launches' \
  --data-urlencode 'question=What launched in developer tools?' \
  --data-urlencode 'window=7d' \
  --data-urlencode 'limit=8'

Request lablive · read only

Try it

Live GET sandbox

This form calls this deployment's read-only context endpoint. It cannot mutate data.

Live read-only sandboxcurrent deployment

Ready24h · limit 5 · ranked citations

Evidence readout

Ask the evidence index

Auto classifies the question, filters the recent evidence window, and returns ranked source records with canonical citation URLs.

window: 24h
limit: 5
mode: read

Resource indexpublic · read-only · JSON

Discovery

Machine resources

01OpenAPI 3.1 specificationTyped operations and schemas for function calling and generated clients./openapi.json →02llms.txt instructionsWhen to use Tech Twitter, evidence recipes, and public source links./llms.txt →03A2A agent cardMachine discovery metadata for the stateless JSON-RPC evidence agent./.well-known/agent-card.json →04Markdown developer guideA compact, agent-readable version of this portal./developers.md →05Printing Press skill + CLIExternal read-only integration for offline search, local evidence, and change-over-time workflows.github · pp-techtwitter →

Error contractapplication/json

Errors

Recover without guessing

REST failures return JSON with a stable code, a readable message, and a concrete hint. Unknown API paths use the same envelope. A2A retains standard JSON-RPC error objects.

{
  "error": {
    "code": "invalid_parameter",
    "message": "Unsupported window",
    "hint": "Use 24h, 48h, or 7d."
  }
}