Look up X Community details by ID — pay-per-request via x402 in USDC on Base
What it does
The `/communities/by/id` endpoint on twit.sh retrieves full details of a specific X (Twitter) Community by its numeric ID. It returns community name, description, member count, join policy, topic, rules, banner image, and admin/creator profiles. According to the provider, this data is not available through the official X API. The endpoint costs $0.0025 USDC per request.
twit.sh is a payment-gated Twitter/X data API that uses the x402 protocol. There are no API keys or accounts required — agents pay per request in USDC on Base mainnet. When an unauthenticated request hits the endpoint, the server responds with HTTP 402 and a machine-readable payment challenge. The caller settles in USDC, retries with a payment proof header, and receives X v2 API-compatible JSON. The API is designed for autonomous AI agents and supports a wide range of X data operations including user lookups, tweet search, list management, and community data.
This specific endpoint is a simple GET request taking a single required query parameter `id` (the numeric community ID). Pagination is not needed for this endpoint since it returns details for a single community. The broader twit.sh API includes companion endpoints for fetching community posts (`/communities/posts`) and community members (`/communities/members`) at $0.01 USDC each.
Capabilities
Use cases
- —Retrieve metadata (name, description, rules, member count) for a specific X Community
- —Monitor community growth by periodically fetching member counts
- —Build dashboards or analytics tools that aggregate X Community information
- —Feed community context into AI agents for social media analysis
- —Discover community admins and creators programmatically
Fit
Best for
- —AI agents needing X Community data without API key setup
- —Developers building X Community analytics or monitoring tools
- —Autonomous workflows that need pay-per-call Twitter data access
Not for
- —High-volume bulk scraping of all X Communities (no discovery/search endpoint for communities)
- —Use cases requiring official X API compliance or OAuth user authorization
- —Fetching community posts or members (use the separate /communities/posts and /communities/members endpoints)
Quick start
curl -X GET "https://x402.twit.sh/communities/by/id?id=1693573582226665701"
# Returns 402 with payment challenge.
# Pay with x402 USDC on Base, then retry with payment proof header:
curl -X GET "https://x402.twit.sh/communities/by/id?id=1693573582226665701" \
-H "X-PAYMENT: <payment_proof>"Endpoint
Quality
Full OpenAPI schema with clear parameter definitions and pricing. The endpoint is live (402 challenge captured). However, no response schema or example response body is documented, and the /docs page returns 404. Pricing and protocol details are well-documented on the landing page.
Warnings
- —No response schema defined — the shape of the 200 response body is undocumented in the OpenAPI spec
- —The /docs endpoint returns 404; documentation is limited to the landing page and OpenAPI
- —The provider claims this data is 'not available in the official X API' — this is unverified
- —Write actions on the broader API require raw Twitter session cookies (auth_token, ct0), which may violate X's Terms of Service
Citations
- —Endpoint costs $0.0025 USDC per requesthttps://x402.twit.sh
- —Returns community name, description, member count, join policy, topic, rules, banner image, and admin/creator profileshttps://x402.twit.sh
- —Not available in the official X APIhttps://x402.twit.sh
- —Payment is in USDC on Base mainnet via x402 protocolhttps://x402.twit.sh
- —No account or API key requiredhttps://x402.twit.sh
- —Returns X v2 API-compatible JSONhttps://x402.twit.sh