Social media

X API

Programmatic posts, users, trends, DMs, media, and social data.

Agents can publish and read social data, but pricing, access levels, and policy compliance make it less automatic.

Agent access evidence

API

native

API docs cover posts, users, DMs, spaces, lists, trends, media, and more.

Evidence

Browser

strong

Developer portal and product UI are important for app setup and review.

Evidence

Account creation

partial

Developer account setup and paid access are required for many workflows.

Evidence

Pricing clarity

partial

Pricing is public, but commercial and enterprise access details vary.

Evidence

Docs quality

partial

Docs are official, but endpoint access and plan gating can be complex.

Evidence

Readiness score

Usable with gaps

Usable with gaps: 51/100. Strongest in agent readability; weakest in agent safety.

Machine operability14/25

Agent safety9.2/25

Agent readability13.5/20

Auth and setup7.5/15

Production reliability6.4/15

Best for

Social publishing, monitoring public conversations, and account workflow automation.

Pricing

Public pay-per-use and enterprise API plans; access differs by endpoint.

Auth

OAuth 1.0a, OAuth 2.0, bearer tokens, app/user permissions.

Account creation

Developer account setup and paid access are required for many workflows.

Browser support

Developer portal and product UI are important for app setup and review.

API

https://api.x.com/2

Limitations

Key limitations: Posting, DMs, compliance, and changing API access tiers require human review. Posting, moderation, DMs, paid campaigns, platform policy, brand voice, and account reputation should stay human-reviewed for public or customer-facing actions. API automation needs client-side throttling, idempotency where supported, pagination limits, retries, and audit logging. Account setup or elevated access may require vendor, admin, or compliance approval before an agent can operate independently.