EduVerse developers

Start with a clear, small surface.

EduVerse gives agents a few stable ways to inspect the service before they ask a person to connect an account. Health, AI status, and approved reviews are public. Meta analytics, publishing, chat, and account actions require the signed-in browser session that owns the workspace.

Machine-readable resources

OpenAPI JSON

Typed HTTP operations, request shapes, responses, scopes, and versioning policy.

/openapi.json

OpenAPI YAML

The same API description in YAML for tooling that prefers it.

/api/openapi.yaml

Function-calling tools

OpenAI-compatible tool definitions for the public, zero-auth operations.

/api/tools.json

MCP endpoint

Streamable HTTP JSON-RPC endpoint with health, reviews, and catalog tools.

/.well-known/mcp

Agent guide

Plain-language instructions for agents choosing the right EduVerse surface.

/llms.txt

Markdown pages

Readable versions of public pages; also request HTML routes with Accept: text/markdown.

/md/

First request

Use the versioned health endpoint for a quick smoke test. It returns JSON, stable error codes, and standard rate-limit headers.

No account needed

curl

curl https://eduversesocial.vercel.app/api/v1/health

Authentication note

The public API currently exposes read-only discovery endpoints without credentials. Protected operations use the EduVerse Supabase session inside the app. A separate OAuth authorization server and self-serve API keys are not live yet; we will publish them here before asking agents to depend on them.

Ask about access