Guide
Agent readiness assessment
A source-based assessment against the SaaStr API Report Card rubric, with explicit implementation gaps.
Estimated score, not an official grade
Reviewed 6 September 2026. SaaStr evaluates documentation and known behavior across six equally weighted categories. This is our source-based estimate; SaaStr has not graded this product, and these scores do not establish its position in their rankings.
Before this documentation pass: 63/100 (B−). With the generated OpenAPI reference, public research guides and reproducible MCP examples verified and published: an estimated 68/100 (B). Public deployment and indexing still need to be verified.
Assessment by category
| SaaStr category | Before | After publication | Evidence and limits |
|---|---|---|---|
| API Design | 7/10 | 8/10 | Versioned REST, strict request contracts and generated OpenAPI. Some success payloads remain explicitly unmodeled. |
| Events & Streaming | 2/10 | 2/10 | No outbound campaign webhooks or business event stream. Inbound Stripe webhooks and MCP response framing do not provide those capabilities. |
| Auth & Security | 8/10 | 8/10 | Tenant, user, client, product/channel and exact action authority. No general per-operation OAuth read/write scopes. |
| Rate Limits | 7/10 | 7/10 | REST limit/reset/remaining and retry headers. Process-local quotas; MCP tool results do not propagate downstream rate metadata. |
| SDKs & Docs | 6/10 | 8/10 | Public HTML/Markdown, OpenAPI, exact MCP contracts and executable examples. No maintained language-specific REST SDK collection. |
| Agent Readiness | 8/10 | 8/10 | Discoverable tools, structured errors, exact approvals and durable consequential retries. Idempotency is operation-specific. |
What a higher score requires
- Outbound signed webhooks with delivery records, retries, replay and subscription controls for campaign, booking, asset and reconciliation changes.
- A resumable business event stream with tenant and scope checks; protocol-level response streaming alone is insufficient.
- Finer read/write scopes in the hosted issuer and API authorization model, applied consistently to every affected operation.
- A broader documented idempotency contract, coordinated quotas and actionable rate metadata through MCP.
- Verified hosted onboarding and controlled supplier campaigns, followed by an independent documentation and behavior review.