Nimble
Nimble is a relationship-focused CRM that unifies contacts, communications, social profiles, calendar, and email into a single workspace for small businesses and sales teams. The platform enriches contact records with social and business data, supports pipeline management, group messaging, and workflow automation across Microsoft 365 and Google Workspace. Nimble's REST API exposes contacts, deals, activities, and tasks via Bearer token authentication for building integrations and syncing CRM data.
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 Nimble the way a machine reads it — 13 machine-readable artifacts across 8 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 — Nimble scores 24.6/100 (emerging), with a separate agent-readiness read of 41/100 (agent aware). 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 Nimble
Each block below is one kind of artifact we hold for Nimble. 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 8
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.
Nimble REST API
REST API for managing contacts, companies, deals, activities, tasks, and notes in Nimble CRM. Authentication uses an API key passed as a Bearer token in the Authorization header.
Nimble Contacts API
The Contacts API from Nimble — 4 operation(s) for contacts.
Nimble Deals API
The Deals API from Nimble — 3 operation(s) for deals.
Nimble Fields API
The Fields API from Nimble — 3 operation(s) for fields.
Nimble Messages API
The Messages API from Nimble — 2 operation(s) for messages.
Nimble Notes API
The Notes API from Nimble — 3 operation(s) for notes.
Nimble Pipelines API
The Pipelines API from Nimble — 3 operation(s) for pipelines.
Nimble Users API
The Users API from Nimble — 1 operation(s) for users.
Scroll within the panel for all 8 ·
Open Collections 1
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).
Nimble CRM API
OPEN COLLECTIONSecurity 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.
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.
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 Nimble — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 3
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/nimble · machine-readable index on apis.io