# Solace — API Agent Score

> Score: 78/100 (Grade: B) | Domain: solace.health | Rubric: 1.0.0 | Checked: September 23, 2026

Solace scored 78/100 (B), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/solace)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 78/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 91/100 (A+)
- Developer Experience: 90/100 (A+)
- Agent Discovery: 92/100 (A+)
- Agent Understanding: 88/100 (A)
- Agent Usability: 48/100 (F)

## Check Results

### API Design

- [pass] Schema coverage & depth — 10/10 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%.
- [pass] Security & governance hygiene — Code is formatter-clean with zero linter errors and zero style warnings. Investigated: sdk 100%, wellknown 50%.
- [warn] Example coverage — README is present but has no runnable quickstart. Investigated: sdk 50%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page found at https://find.solace.health/, but no free tier or sandbox is documented in docs/pricing, so an agent may hit a paywall. Investigated: docs 100%.
- [warn] Description completeness — 2/6 operations lack a description. Investigated: sdk 67%.
- [skip] Quickstart present — No surface produced evidence for this capability in this run.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — A full-corpus llms-full.txt is published at https://solace.health/llms-full.txt, so agents can ingest all your docs in one fetch. Investigated: docs 100%, sdk 0%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/solace, 46331 snippets). Investigated: docs 100%, sdk 100%, cli 0%.
- [warn] Crawlable / AEO — Sitemap has 0 entries but no lastmod values, so crawlers can't tell what changed recently. Investigated: wellknown 50%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [pass] Operation purpose clarity — Read/write classification is partial: 6/6 classified (5 read, 1 write). Investigated: sdk 100%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.
- [skip] Docs structured data — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [warn] Runnable collection with test scripts — README is present but has no runnable quickstart. Investigated: sdk 50%, platform 0%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Solace's API program performs strongly across design, discoverability, developer experience, and agent understanding — partners and their agents can find, read, and evaluate the API surface with confidence. The single critical gap is operational reliability: the SDK ships no built-in retry or idempotency machinery, which means transient failures become partner incidents and AI agents cannot safely automate workflows without guessing at retry behavior. Closing this gap should be the immediate priority to make the program production-ready for partner integrations at scale.