AB Tasty
At AB Tasty, we are your partner for pushing great ideas even further through optimization. We achieve this by empowering brands to build better experiences using personalization, experimentation, recommendations, merchandising, and the market's only emotions-based segmentation solution.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles AB Tasty the way a machine reads it — 80 machine-readable artifacts across 7 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 — AB Tasty scores 63.5/100 (strong), 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 AB Tasty
Each block below is one kind of artifact we hold for AB Tasty. 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 7
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.
AB Tasty Remote Control API
AB Tastys Remote Control API is a developer and QA tool that lets you programmatically drive the AB Tasty SDK from outside your app or page, so you can precisely control and obs...
AB Tasty Public API
The AB Tasty Public API provides programmatic access to manage campaigns, monitor and control experiments, manage account users, and integrate AB Tasty with third-party tools. I...
AB Tasty Activate API
The Activate API from AB Tasty — 1 operation(s) for activate.
AB Tasty Campaigns API
Campaign assignment operations
AB Tasty Environments API
The Environments API from AB Tasty — 3 operation(s) for environments.
AB Tasty Flags API
Feature flag operations
AB Tasty Post API
The Post API from AB Tasty — 4 operation(s) for post.
Scroll within the panel for all 7 ·
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).
AB Tasty Decision API
OPEN COLLECTIONPricing 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.
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.
Ab Tasty 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.
Ab Tasty Finops
FINOPSFeatures 8
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.
A/B Testing
Advanced A/B testing with conversion safety mechanisms and unlimited variations
Feature Flags
Server-side feature flags with targeting and gradual rollouts
Personalization
Experience customization based on emotional needs and engagement segmentation
E-Merchandising
Unified search, recommendations, and product visibility control
Progressive Rollouts
Progressive feature release with automatic KPI-triggered rollbacks
AI Visual Editor
AI-powered prompt-based visual modifications for experiments
AdaptiveCX
Real-time predictive AI for anonymous visitor personalization targeting 90% of visitors
Multivariate Testing
Test multiple variables simultaneously across web and mobile
Scroll within the panel for all 8 ·
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.
Spectral Rules 2
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.
AB Tasty API Rules
SPECTRALAB Tasty API Rules
SPECTRALJSON Schema 13
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.
ActivationRequest
JSON SCHEMABatchActivationItem
JSON SCHEMABatchActivationRequest
JSON SCHEMACampaignRequest
JSON SCHEMACampaignResponseFull
JSON SCHEMACampaignResponseNormal
JSON SCHEMACampaignResponseSimple
JSON SCHEMACampaign
JSON SCHEMACampaignVariation
JSON SCHEMAFlagMetadata
JSON SCHEMAFlag
JSON SCHEMAFlagsResponse
JSON SCHEMASingleCampaignRequest
JSON SCHEMAScroll within the panel for all 13 ·
JSON Structure 13
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Decision Api Activation Request Structure
JSON STRUCTUREDecision Api Batch Activation Item Structure
JSON STRUCTUREDecision Api Batch Activation Request Structure
JSON STRUCTUREDecision Api Campaign Request Structure
JSON STRUCTUREDecision Api Campaign Response Full Structure
JSON STRUCTUREDecision Api Campaign Response Normal Structure
JSON STRUCTUREDecision Api Campaign Response Simple Structure
JSON STRUCTUREDecision Api Campaign Structure
JSON STRUCTUREDecision Api Campaign Variation Structure
JSON STRUCTUREDecision Api Flag Metadata Structure
JSON STRUCTUREDecision Api Flag Structure
JSON STRUCTUREDecision Api Flags Response Structure
JSON STRUCTUREDecision Api Single Campaign Request Structure
JSON STRUCTUREScroll within the panel for all 13 ·
Examples 13
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.
Decision Api Flag Example
EXAMPLEScroll within the panel for all 13 ·
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 6
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.
Web Experimentation
Run A/B tests and multivariate experiments on websites to optimize conversion rates
Feature Experimentation
Multi-channel feature testing across devices via API or SDK implementation
Server-Side Testing
Backend and edge worker experiments using the Decision API
E-commerce Optimization
Merchandising, recommendations, and personalized product experiences
Progressive Deployment
Gradual feature rollouts with automated rollback based on KPI monitoring
Anonymous Personalization
AI-driven real-time personalization for anonymous visitors
Integrations 10
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Google Cloud
Partnership with Google Cloud for infrastructure and analytics integration
Analytics Tools
Connect with analytics platforms via the integration hub for data sharing
CDPs
Customer Data Platform integrations for enhanced visitor profiling
OpenFeature
OpenFeature provider integration for standardized feature flag management
Vercel
Edge function integration with Vercel for server-side experimentation
Cloudflare
Cloudflare Worker integration for edge-based feature experimentation
AWS Lambda
AWS Lambda integration for serverless feature experimentation
Fastly
Fastly worker integration for CDN-level feature experimentation
Akamai
Akamai worker integration for CDN-level feature experimentation
Shopify Hydrogen
Shopify Hydrogen framework integration for headless commerce experimentation
Scroll within the panel for all 10 ·
Resources
Every other property we hold for AB Tasty — 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 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
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
← All providers · Data indexed from github.com/api-evangelist/ab-tasty · machine-readable index on apis.io