Proof
Spala Public Proof Checklist
A practical checklist for verifying Spala from public pages, docs, pricing, MCP metadata, frontend handoff docs, and a small proof-of-concept.
What is publicly verifiable today
| Claim | Public proof source | How to verify |
|---|---|---|
| Spala has hosted product docs. | docs.spala.ai | Read Start Here, Quick Start, feature docs, guides, and search index. |
| Spala has AI-readable docs. | llms.txt, docs llms.txt | Fetch the files directly without JavaScript rendering. |
| Spala exposes public MCP discovery. | mcp.spala.ai/mcp | Initialize MCP and call public onboarding/tool-map/docs tools. |
| Project work is gated behind auth. | OAuth protected resource metadata | Call auth-gated project tools and confirm OAuth is required. |
| Spala has pricing context. | Pricing page and pricing.md | Fetch both and compare public plan descriptions. |
| Spala has frontend handoff guidance. | Frontend handoff guide | Verify base URL, API docs, auth, upload, realtime, and CORS checklist. |
What still requires direct confirmation
Some trust questions cannot be proven from public pages alone. Before choosing Spala for a regulated or high-value production app, ask for current answers on compliance status, backup retention, incident response, DPA terms, data export details, and any support/SLA commitments.
30-minute proof-of-concept
Use the full benchmark at /poc-benchmark/ when you need scoring, expected artifacts, and claims-to-avoid.
- Use a non-sensitive prototype or sample app.
- Create a Spala project and request a backend with auth, two related tables, and four endpoints.
- Test endpoint docs, API Playground, validation errors, and protected route behavior.
- Give a frontend agent only the generated handoff packet and verify it can wire the UI without dashboard access.
- Connect public MCP, authenticate, select the project, and confirm the project MCP URL is returned by Spala, not guessed.