Verify before you commit
Use this page to sanity-check Mastodon quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.
Evidence
Assessed
Docs reviewed · Mar 19, 2026
Freshness
Updated 2026-03-19T20:53:21.068886+00:00
Mar 19, 2026
Failures
Clear
No active failures listed
| Dimension | Score | Bar |
|---|---|---|
| Execution Score Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability. | 7.0 | |
| Access Readiness Score Measures how easily an agent can onboard, authenticate, and start using this service autonomously. | 6.2 | |
| Aggregate AN Score Composite score: 70% execution + 30% access readiness. | 6.8 | |
No active failure modes reported.
Published review summaries with trust provenance attached to each card.
Docs-backed Built from public docs and product materials.
Test-backed Backed by guided testing or evaluator-run checks.
Runtime-verified Verified from authenticated runtime evidence.
Documentation is respectable and more mature than many would expect from a federated social project. The conceptual hurdle is federation and instance variance, not total lack of API material.
Mastodon is useful for agents that need to monitor or participate in federated social networks rather than centralized platforms. It supports timelines, notifications, post creation, and account actions in a way that is conceptually familiar to Twitter-like integrations. Federation adds both resilience and operational complexity.
OAuth-based auth and app registration are standard. That is reasonable for user-account actions, though it creates more setup friction than fixed-key service APIs. For agents operating on behalf of a single organization account, the pattern is manageable.
The API is fairly developer-friendly, and many instance-level flows are approachable for agents. The main complication is that the network is not a single platform with perfectly uniform behavior; instance policy and compatibility can matter. Agents should think in terms of instance-local operations with federated consequences.
Reliability depends partly on the instance you choose. That is the core operational wrinkle: Mastodon is not one uptime envelope but many. Agents can work effectively here, but operational confidence should be tied to the specific instance and role, not to 'Mastodon' as an abstract whole.
Trust shortcuts
This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.
Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.
Overall tier
6.8 / 10.0
No alternatives captured yet.