Open in ChatGPT
View as Markdown

SDKs & Tooling

Not AI does not publish an official client library for the Public REST API in v1. This is a deliberate design choice for v1, not a backlog item.

Why there is no SDK

The Public REST API is designed to be readable and callable directly by both humans and AI agents. Every endpoint is plain HTTPS + JSON, every route is described in the OpenAPI 3.0 spec, and every response uses one of three stable envelopes (single item, paginated collection, or error). An SDK would add a wrapper, a release cadence, and a translation layer between what you wrote and what actually hits the wire. None of those earn their keep for a read-only surface this small.

The OpenAPI document is the SDK. Point your tool of choice at it.

Generate a typed client

The spec is generator-friendly. Any tool that consumes OpenAPI 3.0 will produce a working client.

openapi-generator-cli (Java, Node wrapper available):

npx @openapitools/openapi-generator-cli generate \
  -i https://api.isnotai.com/openapi/v3.json \
  -g typescript-fetch \
  -o ./isnotai-client

The same command supports python, go, csharp-netcore, java, rust, and a few dozen other targets. Swap -g for the language you want.

You can fetch the spec from this site directly:

curl -o swagger.json https://api.isnotai.com/openapi/v3.json

Or use the copy bundled with the docs site at /developers/spec/swagger.json.

Postman

Two options:

  • The Download OpenAPI spec button at the top of the introduction page downloads the bundled OpenAPI 3.0 document for this build. Open Postman, use File → Import, and drop in the file. Postman will scaffold one request per operation. You’ll need to set the Authorization header to Bearer aik_v1_<your-key> on the collection or environment after import.
  • If you’d rather pull the spec straight from a region’s live API, open File → Import → Link in Postman and paste https://api.isnotai.com/openapi/v3.json.

A fully preconfigured Postman collection (with bearer auth wired up out of the box) is tracked as a follow-up alongside the in-browser Try-It explorer rewrite.

HTTPie

For interactive exploration without an SDK or a Postman workspace:

http GET https://api.isnotai.com/v1/integration "Authorization: Bearer $ISNOTAI_API_KEY"
http GET https://api.isnotai.com/v1/sessions    "Authorization: Bearer $ISNOTAI_API_KEY" pageSize==5

curl

The lowest-common-denominator client. Every example in these docs starts as a curl one-liner for exactly this reason.

curl https://api.isnotai.com/v1/sessions \
  -H "Authorization: Bearer $ISNOTAI_API_KEY"

Schema downloads

  • OpenAPI 3.0 JSON, live from the API: https://api.isnotai.com/openapi/v3.json
  • OpenAPI 3.0 JSON, bundled with this site: /developers/spec/swagger.json
  • Swagger UI, when enabled on a deployment: https://api.isnotai.com/swagger

If you would like an SDK

If your organization requires a typed client, generate one from the OpenAPI document above and own it inside your own codebase. That gives you control over the release cadence, the runtime dependencies, and the language version, and it leaves Not AI free to keep the v1 surface stable rather than chase SDK churn.