Canto
Canto is a digital asset management (DAM) platform offering a fully documented REST API for organizing, tagging, distributing, and sharing brand assets including images, videos, and documents across teams and channels. The API uses OAuth 2.0 for authentication and provides endpoints for asset search, metadata management, folder and album operations, automated workflows, and asset distribution.
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 Canto the way a machine reads it — 51 machine-readable artifacts across 19 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 — Canto scores 53.7/100 (developing), with a separate agent-readiness read of 48/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Canto
Each block below is one kind of artifact we hold for Canto. 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 19
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.
Canto bulk_products_catalogs API
Perform bulk products operation on a Product Catalog These endpoints allow you to add or remove products that are associated with a specific product catalog in bulk.
Canto bulk_products_channel_templates API
Perform bulk products operation on a Product Channel Template These endpoints allow you to add or remove products that are associated with a specific channel template in bulk.
Canto dimensions API
The dimensions API from Canto — 2 operation(s) for dimensions.
Canto filter API
API endpoints for filtering product attributes. Allows filtering and retrieving product attributes based on various criteria including: - Exact value matches - Partial text matc...
Canto import_settings API
API endpoints for configuring how CSV imports should be processed. This includes: - Mapping CSV headers to product attributes - Configuring how product variations should be hand...
Canto imports API
API endpoint for importing products from a CSV file. Supports multipart form data uploads with import configuration.
Canto options API
The options API from Canto — 2 operation(s) for options.
Canto product_catalog_products API
The product_catalog_products API from Canto — 2 operation(s) for product_catalog_products.
Canto product_catalogs API
The product_catalogs API from Canto — 2 operation(s) for product_catalogs.
Canto product_categories API
The product_categories API from Canto — 2 operation(s) for product_categories.
Canto product_channel_template_products API
Manage products associated with product channel templates.
Canto product_channel_templates API
Product Channel Templates define the structure and configuration for importing and exporting product data into and out of Canto PIM.
Canto product_custom_attributes API
The product_custom_attributes API from Canto — 2 operation(s) for product_custom_attributes.
Canto product_share_links API
Product Share Links allow you to create shareable links for products that can be accessed outside the PIM system. These links can have custom names and optionally expire.
Canto product_types API
The product_types API from Canto — 2 operation(s) for product_types.
Canto products API
The products API from Canto — 4 operation(s) for products.
Canto variants API
The variants API from Canto — 4 operation(s) for variants.
Canto webhook_events API
The webhook_events API from Canto — 2 operation(s) for webhook_events.
Canto webhooks API
Webhooks are used to notify your application when certain events occur within the system. They can be configured to send a POST request to a specified URL when a specific event ...
Scroll within the panel for all 19 ·
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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Canto Plans Pricing
PLANSRate 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.
Canto 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.
Canto Finops
FINOPSSemantic 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.
Canto 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.
Canto API Rules
SPECTRALJSON Schema 9
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.
catalog
JSON SCHEMAcategory
JSON SCHEMAcustom_attribute_mapping
JSON SCHEMAdimension
JSON SCHEMAproduct_channel_template_summary
JSON SCHEMAproduct_channel_template
JSON SCHEMAproduct_channel_templates_response
JSON SCHEMAproduct_share_link_properties
JSON SCHEMAwebhook_properties
JSON SCHEMAScroll within the panel for all 9 ·
Examples 14
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 14 ·
Security Posture 3
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 Canto — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
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
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/canto · machine-readable index on apis.io