Jinba
Jinba is an enterprise-grade platform for building, running, and deploying AI-powered workflows and agents using natural language. Business teams describe a process in plain language, refine it in a visual graph editor or a YAML manifest, and deploy it to production as an API or an MCP server. The product spans Jinba Flow (the workflow builder), Jinba App / App Neo (the execution and agent environment), and Jinba Toolbox (a centralized tool management and execution platform for AI agents that runs tools in isolated E2B or Daytona sandboxes). For developers, Jinba exposes two REST APIs — the Flow External API for invoking published workflows synchronously or asynchronously, and the Toolbox API for managing organizations, toolsets, tools, versions, runs, webhooks, and API keys — plus a TypeScript SDK, native Model Context Protocol (MCP) endpoints, webhooks with HMAC-signed payloads, and RFC 9457 error semantics. Jinba is SOC 2 Type 2 audited, supports SSO and RBAC, and offers on-premises or private-cloud (AWS/GCP/Azure) deployment. Founded by Shoya Matsumori and Takuya Norisugi; Y Combinator (Winter 2026).
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 Jinba the way a machine reads it — 19 machine-readable artifacts across 14 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 — Jinba scores 53.5/100 (developing), with a separate agent-readiness read of 71/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 Jinba
Each block below is one kind of artifact we hold for Jinba. 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 14
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.
Jinba API Keys API
The API Keys API from Jinba — 2 operation(s) for api keys.
Jinba Credits API
The Credits API from Jinba — 1 operation(s) for credits.
Jinba Execution API
The Execution API from Jinba — 2 operation(s) for execution.
Jinba Explore API
The Explore API from Jinba — 2 operation(s) for explore.
Jinba Flows API
The Flows API from Jinba — 1 operation(s) for flows.
Jinba MCP API
The MCP API from Jinba — 2 operation(s) for mcp.
Jinba Members API
The Members API from Jinba — 1 operation(s) for members.
Jinba Organizations API
The Organizations API from Jinba — 2 operation(s) for organizations.
Jinba Public API
The Public API from Jinba — 2 operation(s) for public.
Jinba Runs API
The Runs API from Jinba — 2 operation(s) for runs.
Jinba Tools API
The Tools API from Jinba — 2 operation(s) for tools.
Jinba ToolSets API
The ToolSets API from Jinba — 2 operation(s) for toolsets.
Jinba Versions API
The Versions API from Jinba — 3 operation(s) for versions.
Jinba Webhooks API
The Webhooks API from Jinba — 3 operation(s) for webhooks.
Scroll within the panel for all 14 ·
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.
jinba-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Jinba Toolbox Webhooks
ASYNCAPISecurity Posture 2
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Jinba — 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 1
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 2
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/jinba · machine-readable index on apis.io