VALAR Developer Resources
Every public VALAR surface an agent or developer can call, at predictable URLs. The authenticated product API lives separately at api.valar.space and is documented at docs.valar.space.
Surfaces
- Product documentation
Full API reference and platform guides for the authenticated VALAR product API at api.valar.space.
https://docs.valar.space/ - OpenAPI specification
OpenAPI 3.1 description of every public valar.space endpoint, each with a unique operationId and typed schemas — ready for LLM function calling.
/openapi.json - MCP server (Streamable HTTP)
Read-only Model Context Protocol server. Tools: valar_get_pricing, valar_get_homepage, valar_get_site_map, valar_get_changelog_latest, valar_get_docs_index.
/mcp - MCP server manifest
MCP registry manifest for the VALAR MCP server.
/server.json - MCP discovery
Domain-level discovery pointing at the canonical MCP server card (/.well-known/mcp/server-card.json).
/.well-known/ai-catalog.json - API catalog
RFC 9727 linkset pointing at the product API description, human documentation and status endpoint.
/.well-known/api-catalog - Pricing markdown
Agent-readable pricing tiers with per-tier capability depth.
/pricing.md - llms.txt
When-to-use guidance for agents and the full resource index.
/llms.txt - Homepage markdown
The homepage as plain markdown — also served at / on an Accept: text/markdown request.
/.well-known/homepage-markdown
Calling the MCP server
Connect any Streamable HTTP MCP client to https://valar.space/mcp — no authentication, stateless JSON-RPC over POST. Example handshake:
curl -X POST https://valar.space/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Rate limits
Public endpoints allow 60 requests per 60 seconds per client. Responses carry the IETF RateLimit-Policy and RateLimit headers so callers can self-throttle; an exhausted window answers 429 with a numeric Retry-After.
Errors
API errors return structured JSON following RFC 9457 problem details with stable code, human-readable detail, and actionable resolution fields — never HTML pages. Unknown paths answer 404; unsupported methods answer 405 with Allow.
Ready to evaluate the platform? Book a technical walkthrough.