Developers

Build on KIN Create with an API and MCP.

A versioned REST API documented with OpenAPI 3.1, plus a read-only, tenant-authorized MCP server so AI agents like Claude can work with your KIN Create data safely.

Model Context Protocol

A governed MCP server for AI agents

KIN Create ships a read-only MCP server so an AI agent can read the right data on a user's behalf — under the same tenant isolation and permission rules as the app, and with nothing ever written back. It runs locally over stdio today (there is no hosted endpoint yet).

Available tools

  • kincreate.campaigns.summary

    A bounded, minimized summary of the caller's own campaigns (id, name, status, budget).

  • kincreate.confidence.read

    A creator's explainable audience-confidence score: score, band, factors and limitations.

  • kincreate.creator.profile

    A creator's public, discoverable marketplace profile (display name, headline, categories, platforms, reach).

Security model

  • Local transport today: runs over stdio for a local MCP client; there is no hosted/remote endpoint yet.
  • Read-only: every tool is side-effect-free (no writes, ever).
  • Feature-gated: disabled unless explicitly enabled.
  • Identity via the transport session (signed token + tenant), never via tool arguments.
  • Explicit, revocable access grants — revocation fails closed.
  • Per-tool authorization reuses the same role/permission matrix as the app.
  • Per-user / per-tenant / per-tool rate limiting.
  • Bounded, minimized, redacted output; immutable audit with no payload.
  • Untrusted content: retrieved records are inert data, never interpreted as instructions.

The MCP server is feature-gated and off by default, and today runs locally over stdio — a hosted/remote transport is on the roadmap. Questions or want to follow its progress? Contact us.

REST API

Versioned REST API, documented with OpenAPI

Every endpoint lives under /api/v1. Most require a Bearer session token and are tenant-scoped; authorization follows the role/permission matrix, and unauthorized or cross-tenant access returns a non-disclosing response. The reference below is generated from the live routes.

Loading API reference…

Field-level request/response schemas are being added to the spec incrementally. Payment endpoints currently operate in a provider sandbox (test mode).