Tackle
Tackle is a Cloud Go-To-Market (Cloud GTM) platform that helps software companies sell through the AWS, Microsoft Azure, and Google Cloud marketplaces. Its developer APIs (developers.tackle.io) automate the full marketplace workflow: creating and managing private offers on AWS and Microsoft, AWS Partner Central co-sell opportunities and invitations, public contracts, metered usage reporting, disbursements and invoices, buyer prospecting (propensity-to-buy domain scoring), and SCIM 2.0 user provisioning. Authentication is machine-to-machine JWT (client_id/client_secret exchanged for a Bearer token), and vendors receive marketplace lifecycle events via registered, authenticated webhooks. Tackle is backed by a16z and publishes a SafeBase trust center (SOC 2 Type II, GDPR).
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 Tackle the way a machine reads it — 32 machine-readable artifacts across 25 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 — Tackle scores 56.2/100 (developing), with a separate agent-readiness read of 75/100 (agent native). 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 Tackle
Each block below is one kind of artifact we hold for Tackle. 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 25
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.
Tackle Authentication API
Operations for API Authentication
Tackle Contracts API
The Contracts API from Tackle — 2 operation(s) for contracts.
Tackle Currencies API
Microsoft marketplace currency and conversion helpers.
Tackle Disbursements API
The Disbursements API from Tackle — 1 operation(s) for disbursements.
Tackle Entitlements API
Legacy entitlements endpoint - returns flat role objects
Tackle Groups API
SCIM 2.0 Groups endpoint - returns full Group resources (RFC 7643 §4.2)
Tackle Invitations API
Create (test-environment-only), read, update, and list co-sell invitations — AWS-led requests to partner with you on a specific opportunity. Use the update operation to accept o...
Tackle Invoices API
The Invoices API from Tackle — 1 operation(s) for invoices.
Tackle Marketplace API
AWS Marketplace context endpoints used to assemble offers and amendments.
Tackle Metering API
The Metering API from Tackle — 2 operation(s) for metering.
Tackle Notifications API
Buyer instruction notification operations.
Tackle Opportunities API
Create, read, update, and list co-sell opportunities — the partner- originated (Outbound / Partner Referral) and AWS-originated (Inbound / AWS Referral) deals tracked in AWS Par...
Tackle Partners API
AWS Marketplace partner (reseller) reference data.
Tackle Private Offer Actions API
Private offer lifecycle actions such as archive, cancel, and sync.
Tackle Private Offers API
AWS private-offer lifecycle (create, read, update, cancel, push to marketplace).
Tackle Products API
Operations for Products
Tackle public API
The public API from Tackle — 7 operation(s) for public.
Tackle Registrations API
Operations for Order Registrations
Tackle Scores API
Score domains and search scored accounts.
Tackle Service Provider API
Service provider configuration and capabilities
Tackle Solutions API
List the co-sell solutions registered with AWS Partner Central for your account. Solution identifiers are referenced by `solutions` on opportunities.
Tackle Subscriptions API
Operations for Subscriptions
Tackle Users API
User management operations
Tackle Version API
Operations for API Versions
Tackle Webhooks API
Operations for Webhooks
Scroll within the panel for all 25 ·
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.
tackle-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.
Tackle Webhooks
ASYNCAPISecurity 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.
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 Tackle — 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 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Access & Security 5
Authentication, authorization, and security posture
Operate 3
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/tackle · machine-readable index on apis.io