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 — 34 machine-readable artifacts across 2 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 42.0/100 (developing), with a separate agent-readiness read of 33/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Jinba's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/jinba/"
title="Jinba on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/jinba.svg"
alt="Jinba Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/jinba/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/jinba/"
title="Jinba on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/jinba/card.svg"
alt="Jinba Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
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 ·
Open Collections 15
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONJinba Flow External API Keys API
OPEN COLLECTIONJinba Flow External API Keys Credits API
OPEN COLLECTIONJinba Flow External API Keys Execution API
OPEN COLLECTIONJinba Flow External API Keys Explore API
OPEN COLLECTIONJinba Flow External API Keys Flows API
OPEN COLLECTIONJinba Flow External API Keys MCP API
OPEN COLLECTIONJinba Flow External API Keys Members API
OPEN COLLECTIONJinba Flow External API Keys Organizations API
OPEN COLLECTIONJinba Flow External API Keys Public API
OPEN COLLECTIONJinba Flow External API Keys Runs API
OPEN COLLECTIONJinba Flow External API Keys Tools API
OPEN COLLECTIONJinba Flow External API Keys ToolSets API
OPEN COLLECTIONJinba Flow External API Keys Versions API
OPEN COLLECTIONJinba Flow External API Keys Webhooks API
OPEN COLLECTIONScroll within the panel for all 15 ·
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 Server
Jinba Toolbox provides native Model Context Protocol (MCP) endpoints that expose any toolset as an MCP-compatible server. Each MCP-enabled toolset becomes an MCP server reachabl...
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 4
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/jinba · machine-readable index on apis.io
This is an independent, third-party profile of Jinba, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.