Naboo
Naboo is Reasoning Layer infrastructure for enterprise AI agents, built on a Decision Graph that models how a company actually decides, ships, and unblocks - who decided what, what triggered each decision, what blocks it, and what depends on it - across code, tickets, pull requests, docs, Slack, runtime, and internal services. Any AI agent in the organization queries the graph in GraphQL, or through an MCP server that turns plain intent into a structured query, and gets a structured answer instead of a list of search results. Naboo deploys on-premise or in a customer VPC with zero data egress, integrates with any LLM (OpenAI, Anthropic, Llama, Mistral) and agentic framework (LangChain, AutoGen, CrewAI), and enforces existing role-based access controls at retrieval time. Founded in 2023 by Gilad Salinger (CEO) and Dror Wolmer (CTO), with production customers Global-E (NASDAQ: GLBE) and Melio.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Naboo the way a machine reads it — 2 machine-readable artifacts, 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 — Naboo scores 16.8/100 (emerging), with a separate agent-readiness read of 0/100 (human only). 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 Naboo
Each block below is one kind of artifact we hold for Naboo. 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.
Security 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.
Resources
Every other property we hold for Naboo — 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 1
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 3
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/naboo · machine-readable index on apis.io