Developers

Integrate NOVAASTRA with REST APIs, API keys, MCP tools, and the NovaCoder IDE. All authenticated traffic uses /api/v1 unless noted.

Authentication

JWT from login or OAuth — send Authorization: Bearer …
API keys (Pro+) — header X-API-Key
Multi-tenant: X-Tenant-ID when your workspace requires it

OAuth password grant (testing)

curl -X POST "https://novaastra.in/api/v1/auth/token" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  -d "username=YOUR_USER&password=YOUR_PASSWORD"

Query API

Primary chat/completion entrypoint. Rate limits follow your plan.

JWT query

curl -X POST "https://novaastra.in/api/v1/query/" \
  -H "Authorization: Bearer YOUR_JWT" \
  -H "Content-Type: application/json" \
  -d '{"query": "Hello NOVA", "model": "auto"}'

API key query

curl -X POST "https://novaastra.in/api/v1/query/" \
  -H "X-API-Key: novaastra_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "Hello", "model": "auto"}'

MCP and agents

Autonomous MCP plane is exposed at /mcp/v1/* (tool list, tool call with human-in-the-loop consent for high-risk tools). Agent runtime endpoints power NovaCoder and cross-device executor flows — beta surfaces; expect evolving schemas.

Agent capabilities overview

Keys and docs

Create account Manage API keys (sign in)NovaCoder IDE

Operator guides live in the repository under docs/ (API usage, deployment). OpenAPI is disabled on production for hardening; use staging for schema export.