Stripe Integrations Page Using Naftiko Capabilities

These Naftiko capabilities are designed to help us think differently about how API service providers publish and operate their integrations — in an age where most "integration pages" are static lists meant for humans, not for the agents that increasingly drive them.

Each capability below is a declarative YAML manifest that describes a real integration workflow with Stripe (and the other systems involved). They’re fully executable: you pull the YAML, run it under the Naftiko Framework in a Docker container, and you have a working integration end-to-end — no boilerplate code, no glue project, no copy/paste from a quick-start page.

Top 50 integrations Executable Declarative YAML Run in Docker Agent-discoverable
Naftiko Framework on GitHub → Browse YAML source → Back to Stripe
Navi, the Naftiko mascot
How it runs. Each capability is executable using Docker via the Naftiko Framework. Clone the repo, point Naftiko at a capability YAML, and the framework provisions the runtime, handles credentials, and orchestrates the calls.

Capabilities

Loading Stripe integrations…

Why this matters

For API producers

Your "integrations" page stops being a static screenshot wall. Every integration is a versioned, testable, agent-runnable artifact. New partners can wire themselves in by authoring a YAML file — you don’t carry the maintenance burden of bespoke integration code, and agents can verify against your contract instead of guessing from marketing copy.

For API consumers

Skip the “read the docs, write the glue, deploy it” cycle. Pull a capability, run it under Naftiko, and the integration is live. The capability YAML doubles as machine-readable documentation of exactly which Stripe operations and external systems are touched, with clear inputs, outputs, and side effects.

For AI agents

Capabilities are addressable, executable, and self-describing — the three things an agent needs to act with confidence. Agents can discover the catalog via the discover-integrations skill, plan against capability schemas, and execute without bespoke per-vendor wiring.

Adding a new integration

New integrations are pure data — commit a YAML file to the integrations/ folder of api-evangelist/stripe and it shows up here on the next page load. No code, no CI hooks per integration, no provider-side review queue.