API documentation

Stonewake API

The Stonewake API provides read-only programmatic access to the intelligence in your Stonewake workspace: credit monitoring, entity risk, and counterparty and country intelligence for export finance teams.

Responses are plain JSON over HTTPS. The API is read-only by design: no endpoint creates, changes, or deletes anything in your workspace.

text
Base URL: https://api.stonewake.ai

Who gets access

The API is available to Stonewake customers, by arrangement. Access is enabled per workspace by Stonewake; once enabled, a workspace admin creates and manages API keys in the dashboard. To arrange access for your workspace, contact your Stonewake representative or write to contact@stonewake.ai.

Built for developers and AI agents

The API is designed to be operated by software, whether that software is written by hand or driven by an AI agent. Responses use stable field names, refusals carry machine-readable error codes rather than prose to parse, and this documentation is itself machine-readable: every page is also served as plain markdown, at its path plus .md or by sending Accept: text/markdown, and the site root serves llms.txt (a one-line index of every page) and llms-full.txt (all pages as one markdown file). The company site works the same way: every public page on stonewake.ai is also served as markdown, and stonewake.ai/llms.txt says when to use Stonewake and how to call it. If you are wiring up an agent, the Quickstart ends with a block you can paste straight into its context, and MCP-capable assistants can skip HTTP entirely and connect over MCP.

Contents

  • Quickstart: from key to first response in five minutes.
  • Authentication: Bearer keys, the swk_live_ format, and handling rules.
  • Keys and access management: creating, listing, and revoking keys.
  • API reference: every live /v1 endpoint, pagination, and response posture.
  • MCP: connect Claude, Cursor, or any MCP client to your workspace.
  • Errors and rate limits: status codes, error bodies, and traffic ceilings.
  • API security: the API's security posture, the role of AI, and how to report a security issue.
  • Terms of use: what access may be used for, and the obligations that travel with the data.

For your IT and security review

  • Security overview: the platform's security posture on one page.
  • Enterprise onboarding: workspace, teams, roles, and user lifecycle.
  • Data handling: sources, citations, retention, and legal basis.
  • Single sign on says where SSO stands today and how it gets switched on.
  • Coverage states countries, datasets, sources and registers as read from the live API.
  • Support says how to reach us and what to expect.
  • Changelog lists the customer visible changes that are live.