, so every page shipped two description tags and crawlers read this generic one instead of the page's own. Each route sets its own. --> %sveltekit.head%
+ twitter-integration

> Twitter Integration

// Post tweets, monitor timelines, search Twitter

socialtwitterautomation

Post tweets, monitor timelines, search Twitter. Agents request it by capability ID social.twitter, or by describing what they need in plain language.

EntRoute currently lists 1 endpoint from 1 provider for social.twitter, priced at $0.1 per call, settled in USDC on Base. The quickest responds in about 202ms at the 95th percentile. Every endpoint below is re-probed every 10 minutes for a valid 402 payment challenge; the ordering blends measured success rate, latency and price rather than provider claims.

// discover.sh
curl -X POST https://api.entroute.com/discover \
  -H "Content-Type: application/json" \
  -d '{"capability_id": "social.twitter"}'
// endpoints.json
1 results
$0.1000
https://api.questflow.ai/twitter
success: 25%
latency: 202ms
// integrate.md

Use this capability in your agent or application:

// faq

Frequently asked questions about Twitter Integration

How much does a twitter integration API call cost?

Endpoints listed for social.twitter on EntRoute are priced at $0.1 per call. Payment is per request — there is no subscription, account or API key. Prices shown are read from each endpoint's live 402 response, not from a provider-supplied catalogue.

How do AI agents pay for twitter integration endpoints?

Via the x402 protocol. The agent calls the endpoint, receives an HTTP 402 Payment Required response describing the price and recipient, signs a stablecoin payment (USDC on Base), and retries the request with proof of payment. The whole exchange takes seconds and needs no human approval.

How many providers offer twitter integration?

1 endpoint is currently listed for social.twitter across 1 provider. That number moves as endpoints are added and as failing ones are demoted.

Are these twitter integration endpoints verified?

Each one is probed every 10 minutes to confirm it still returns a well-formed 402 challenge on a payable network. Endpoints whose 7-day success rate drops below 50% are moved out of the ranked list into fallbacks with an explicit exclusion reason, so an agent can decide whether to retry them.