Insforge
InsForge is an open-source (Apache-2.0), agent-native cloud infrastructure platform built so that AI coding agents can provision and operate an entire backend end to end through a CLI and packaged agent skills instead of a human clicking through a dashboard. A single project bundles a Postgres database with schema management and row-level security, authentication (users, sessions, OAuth, JWT), S3-compatible object storage, Deno-based edge functions with cron, a unified AI model gateway, realtime subscriptions and webhooks, long-lived custom compute, frontend hosting via Vercel, transactional email, and payments via Stripe and Razorpay. The REST API is documented as fourteen OpenAPI 3.0 service specifications and is driven by an official TypeScript SDK, CLI, and hosted MCP server. InsForge is a Y Combinator company.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Insforge the way a machine reads it — 16 machine-readable artifacts across 11 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Insforge scores 57.2/100 (developing), with a separate agent-readiness read of 66/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Insforge
Each block below is one kind of artifact we hold for Insforge. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 11
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Insforge Admin API
The Admin API from Insforge — 54 operation(s) for admin.
Insforge Channels API
Configure realtime channel patterns, webhooks, and availability.
Insforge Client API
The Client API from Insforge — 35 operation(s) for client.
Insforge Configuration API
Manage realtime retention settings.
Insforge Messages API
Inspect realtime message history and delivery stats.
Insforge Payment Webhooks API
Provider webhook ingestion routes
Insforge Permissions API
Manage helper endpoints for realtime RLS examples.
Insforge Razorpay Payments API
Razorpay Orders, Subscriptions, catalog, manual webhook setup, sync, customer, and transaction routes
Insforge S3 Access Keys API
The S3 Access Keys API from Insforge — 3 operation(s) for s3 access keys.
Insforge S3 Protocol API
The S3 Protocol API from Insforge — 1 operation(s) for s3 protocol.
Insforge Stripe Payments API
Stripe Checkout, Billing Portal, catalog, sync, customer, subscription, and transaction routes
Scroll within the panel for all 11 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
insforge-mcp.yml
MCP SERVERSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Insforge — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/insforge · machine-readable index on apis.io