Enterprise API

API overview

The Obsidian enterprise API is a REST interface to the same verified regulatory database that powers the MCP — for feeds, internal tools and data pipelines, authenticated with an API key.

Base URL

https://api.obsidianri.com

All endpoints are served over HTTPS and return JSON.

Authentication

Every request must carry an API key (keys look like sk-…). Send it in the X-API-Key header, or as a bearer token:

curl https://api.obsidianri.com/frameworks \
  -H "X-API-Key: sk-your-key-here"

Full details, including how to create and rotate keys, are in Authentication.

Your first request

Search the regulatory database with a natural‑language query:

curl https://api.obsidianri.com/search \
  -H "X-API-Key: sk-your-key-here" \
  --data-urlencode "q=CSRD reporting obligations" \
  --data-urlencode "jurisdiction=EU" \
  -G

Conventions

• Format. All responses are JSON. Send query parameters in the URL for GET requests.
• Scoping. Results are limited to the industries your account covers, exactly like the MCP.
• Errors. Standard HTTP status codes — 401 for a missing or invalid key, 402 when you are over your plan limit, 404 for an unknown id.
• Metering. One request to a data endpoint counts as one verified request against your plan.