The Twitter namespace is a direct typed scraper family, not a generic web scrape.
Live route family
/v1/crawl/twitter/profile/v1/crawl/twitter/tweets/v1/crawl/twitter/search/v1/crawl/twitter/tweet- raw REST routes also exist for
transcript,community, andcommunity_tweets
Example
Read a profile
```bash
curl 'https://api.faircompany.ai/v1/crawl/twitter/profile?handle=openai' \
-H "Authorization: Bearer fc_live_xxx"
```
```ts
const profile = await fc.twitter.profile({
handle: "openai",
});
console.log(profile.handle);
console.log(profile.followers);
```
```python
import httpx
import os
api_key = os.environ.get("FAIRCRAWL_API_KEY", "fc_live_xxx")
response = httpx.get(
"https://api.faircompany.ai/v1/crawl/twitter/profile",
headers={"Authorization": f"Bearer {api_key}"},
params={"handle": "openai"},
timeout=30,
)
response.raise_for_status()
print(response.json()["handle"])
```
```json
{
"tool": "faircrawl_research",
"arguments": {
"query": "openai site:x.com",
"sources": ["twitter"],
"limit": 5
}
}
```
Notes
- use the typed Twitter routes when you already know the handle or tweet URL
- use
/researchwithsources: ["twitter"]for broader topic discovery - the TypeScript SDK wraps
profile,tweets,search, andtweet