PolyAPI
Poly, built using cutting-edge AI and Kubernetes-native technology, accelerates development and simplifies the operation of integrations, orchestrations, and microservices with TypeScript, Python, Java, and C.
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 PolyAPI the way a machine reads it — 144 machine-readable artifacts across 1 API, 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 — PolyAPI scores 49.1/100 (developing), with a separate agent-readiness read of 24/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. 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 PolyAPI'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/polyapi/"
title="PolyAPI on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/polyapi.svg"
alt="PolyAPI Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/polyapi/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/polyapi/"
title="PolyAPI on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/polyapi/card.svg"
alt="PolyAPI 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 PolyAPI
Each block below is one kind of artifact we hold for PolyAPI. 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 10
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.
PolyAPI API Functions API
Manage API functions that wrap third-party API calls and are invoked through the PolyAPI gateway.
PolyAPI Assistants API
Manage AI assistants and conversations for AI-powered document assistance and discovery.
PolyAPI Client Functions API
Manage shared client functions that run wherever they are executed.
PolyAPI Environments API
Manage environments for organizing and deploying resources across development, staging, and production.
PolyAPI Jobs API
Manage jobs that execute functions at a set time, interval, or CRON schedule.
PolyAPI Schemas API
Manage shared JSON Schema definitions used to type events and application data.
PolyAPI Server Functions API
Manage Knative serverless functions that run in the PolyAPI cloud infrastructure.
PolyAPI Triggers API
Manage triggers that connect cloud events to functions for event-driven execution.
PolyAPI Variables API
Manage variables and secrets that are stored securely and injected into functions at runtime.
PolyAPI Webhooks API
Manage webhook endpoints that receive events via HTTP calls, with support for authentication and custom listeners.
Scroll within the panel for all 10 ·
Postman Collections 10
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Scroll within the panel for all 10 ·
Open Collections 12
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 COLLECTIONPolyAPI Platform API Functions API
OPEN COLLECTIONPolyAPI Platform API Functions Assistants API
OPEN COLLECTIONPolyAPI Platform API Functions Client Functions API
OPEN COLLECTIONPolyAPI Platform API Functions Environments API
OPEN COLLECTIONPolyAPI Platform API Functions Jobs API
OPEN COLLECTIONPolyAPI Platform API
OPEN COLLECTIONPolyAPI Platform API Functions Schemas API
OPEN COLLECTIONPolyAPI Platform API Functions Server Functions API
OPEN COLLECTIONPolyAPI Platform API Functions Triggers API
OPEN COLLECTIONPolyAPI Platform API Functions Variables API
OPEN COLLECTIONPolyAPI Platform API Functions Webhooks API
OPEN COLLECTIONScroll within the panel for all 12 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Polyapi Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Polyapi Finops
FINOPSFeatures 68
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Catalog
Devleopment
Operations
Integrations
Microservices
Orchestrations
Event Management
Generate Documentation
Observe in Postman
Ingest OpenAPI
Generate Schema
Generate Functions
Intellisense
Type Safety
Credital Management
Secrets Vault
GitHub Copilot
Generate Code Examples
Logs
Dashboards
Error Handling
Even tStreaming
Activity History
Smarter Python Integrations that Help You Process Data Faster
Tooltips, Date Pickers, Smarter 404s
Function Owners and States
Improved Search for API Functions in PolyAPI
New Tixr API Operations Now Available in PolyAPI
Schema Injection for Smarter Code Suggestions
Function Replication Now Includes Schemas
Python Snippets in PolyAPI
Schema References and Visibility
Improving Server Function Wakeup Speed
Single Sign-On (SSO)
Tooltips for Canopy Applications
Clickable Poly Tree Links for Public Functions
API Keys Post Expiration Window
Function Lifecycle States
OAS Training HostUrl Improvements
Unique Variable IDs Introduced
System Health Status Page
Environment-Level Applications
Accelerate Your Mews Integration
Environment Contexts and Names
Public API Function Replication
Enhance Your Salesforce Marketing Cloud Workflows
API Key Expiry and Rotation
Empowering API Developers with AI-Powered Document Assistance
Variables and Triggers in Activity History
Project Glide Support for Python
Webhook Triggering Params Parsing
GitLab Support
SFX Execution Key (TS)
Configuring Error Handlers
Enhanced Schema Management and Reusability
ContextName, An Important Keystone Attribute
Fine-Grained Admin Permissions
Reusable Schema Models in Node
PolyAPI integration with Zoom
Node Improvements
PolyAPIs Canopy Experience
Shared Metrics
Using PolyAPIs Postman Collection
Magic UI Configuration with Canopy
Function Invocation via UI
Function Code Copying
Function Replication
Error Events to Server Function Triggers
Scroll within the panel for all 68 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Polyapi Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
PolyAPI API Rules
SPECTRALJSON Schema 10
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
PolyAPI API Function
JSON SCHEMAPolyAPI Assistant Conversation
JSON SCHEMAPolyAPI Client Function
JSON SCHEMAPolyAPI Environment
JSON SCHEMAPolyAPI Job
JSON SCHEMAPolyAPI Schema
JSON SCHEMAPolyAPI Server Function
JSON SCHEMAPolyAPI Trigger
JSON SCHEMAPolyAPI Variable
JSON SCHEMAPolyAPI Webhook
JSON SCHEMAScroll within the panel for all 10 ·
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.
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.
Use Cases 26
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Service Development
Operational Applications
Workflow Automation
Vendor Management
Partner Enablement
Generate SDKs
Monitor Usage & Issues
AI Powered Discovery
Service Development
Enable Development
Orchestrate Anything
Easy & Secure Access
Operational Applications
Function-Driven UI
Data & Actions
Easy & Secure Access
Custom Tables
Store references and operational
Workflow Automation
Receive or Pull Data
Transform & Route
Easy & Secure Access
Vendor Management
Common Interfaces
Decouple & Transform
Vendor Monitoring
Scroll within the panel for all 26 ·
Resources
Every other property we hold for PolyAPI — 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 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/polyapi · machine-readable index on apis.io
This is an independent, third-party profile of PolyAPI, 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.