VSCO
VSCO is a photography company whose mobile apps and community give photographers editing tools, presets, and a place to share their work. Its business product, VSCO Workspace (the former Tave studio-management platform), ships a public REST API — the VSCO Workspace API v2 — that exposes a studio's contacts, jobs, orders, quotes, payments, events, galleries, files, and REST Hook webhook subscriptions behind API-key authentication, with a published OpenAPI 3.0 definition and Redoc reference.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles VSCO the way a machine reads it — 38 machine-readable artifacts across 34 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 — VSCO scores 44.8/100 (thin), with a separate agent-readiness read of 57/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.
How we profile VSCO
Each block below is one kind of artifact we hold for VSCO. 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 34
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.
VSCO Brands API
The Brands API from VSCO — 2 operation(s) for brands.
VSCO Contacts API
The Contacts API from VSCO — 2 operation(s) for contacts.
VSCO Custom Fields API
The Custom Fields API from VSCO — 2 operation(s) for custom fields.
VSCO Discount Types API
The Discount Types API from VSCO — 2 operation(s) for discount types.
VSCO Discounts API
The Discounts API from VSCO — 2 operation(s) for discounts.
VSCO Event Types API
The Event Types API from VSCO — 2 operation(s) for event types.
VSCO Events API
The Events API from VSCO — 2 operation(s) for events.
VSCO File Types API
The File Types API from VSCO — 2 operation(s) for file types.
VSCO Files API
The Files API from VSCO — 2 operation(s) for files.
VSCO Galleries API
The Galleries API from VSCO — 2 operation(s) for galleries.
VSCO Job Closed Reasons API
The Job Closed Reasons API from VSCO — 2 operation(s) for job closed reasons.
VSCO Job Contacts API
The Job Contacts API from VSCO — 2 operation(s) for job contacts.
VSCO Job Payment API
The Job Payment API from VSCO — 1 operation(s) for job payment.
VSCO Job Roles API
The Job Roles API from VSCO — 2 operation(s) for job roles.
VSCO Job Types API
The Job Types API from VSCO — 2 operation(s) for job types.
VSCO Job Worksheets API
The Job Worksheets API from VSCO — 2 operation(s) for job worksheets.
VSCO Jobs API
The Jobs API from VSCO — 3 operation(s) for jobs.
VSCO Lead Sources API
The Lead Sources API from VSCO — 2 operation(s) for lead sources.
VSCO Lead Statuses API
The Lead Statuses API from VSCO — 2 operation(s) for lead statuses.
VSCO Notes API
The Notes API from VSCO — 2 operation(s) for notes.
VSCO Orders API
The Orders API from VSCO — 3 operation(s) for orders.
VSCO Payment Methods API
The Payment Methods API from VSCO — 2 operation(s) for payment methods.
VSCO Payments API
The Payments API from VSCO — 3 operation(s) for payments.
VSCO Product Types API
The Product Types API from VSCO — 2 operation(s) for product types.
VSCO Products API
The Products API from VSCO — 2 operation(s) for products.
VSCO Profit Centers API
The Profit Centers API from VSCO — 2 operation(s) for profit centers.
VSCO Quotes API
The Quotes API from VSCO — 2 operation(s) for quotes.
VSCO Rest Hooks API
Webhooks based on Zapier's now-deprecated REST Hooks specification.
You can use t...
VSCO Schedulers - Client Access API
The Schedulers - Client Access API from VSCO — 1 operation(s) for schedulers - client access.
VSCO Studio API
The Studio API from VSCO — 2 operation(s) for studio.
VSCO Tax Groups API
The Tax Groups API from VSCO — 2 operation(s) for tax groups.
VSCO Tax Rates API
The Tax Rates API from VSCO — 2 operation(s) for tax rates.
VSCO Timezones API
The Timezones API from VSCO — 2 operation(s) for timezones.
VSCO Users API
The Users API from VSCO — 2 operation(s) for users.
Scroll within the panel for all 34 ·
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.
vsco-mcp.yml
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.
Vsco Workspace 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.
Resources
Every other property we hold for VSCO — 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
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 3
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 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/vsco · machine-readable index on apis.io