Integration and best practices
Use inttegro to choose an API, SDK, Checkout, or MCP approach. Use inttegro-best-practices for authentication, money handling, idempotency, retries, pagination, privacy, and observability.
Explore integration guidanceReusable guidance for coding agents
Add public Inttegro skills to a compatible coding agent for integration design, Checkout, testing, debugging, upgrades, and state synchronization. Give it reusable instructions grounded in the platform’s documented contracts.
Keep busy checkouts dependable
Reuse the gift order if a customer taps Pay twice. I’d verify these three cases before the gift campaign.
Your flow needs a clearer ending when payment takes longer. Keep the same order and tell the customer you’re checking it.
Eight public skills
Skills give an agent a repeatable way to approach Inttegro work: what to inspect, which references to read, and what to verify. Use the broad integration skill for a new project or a focused skill for a specific change.
These are developer instructions, not credentials or a connection to merchant data. You can review their public source before adding them to a compatible tool.
Use inttegro to choose an API, SDK, Checkout, or MCP approach. Use inttegro-best-practices for authentication, money handling, idempotency, retries, pagination, privacy, and observability.
Explore integration guidanceUse inttegro-checkout for the customer payment journey. Use inttegro-state-sync for authoritative lookup, polling, and reconciliation so a redirect or timeout is not mistaken for payment success.
Explore state synchronizationUse inttegro-testing to plan safe fixtures and end-to-end checks. Use inttegro-debug to investigate recorded evidence, request failures, state mismatches, and integration boundaries.
Explore testing guidanceUse upgrade-inttegro when SDK or contract changes affect an integration. Use inttegro-mcp for agent connections, authentication, structured results, confirmation, and host capabilities.
Explore MCP guidanceBuild with the right guidance
Use the Checkout skill to build the buying flow, state-sync to check payment, and testing to cover retries before launch.
I’d make the return page check the order with Inttegro, then show a clear message for each outcome—not just assume the payment worked.
A focused starting point
Customers sometimes tap Pay twice. Help me make sure that creates just one gift order, and that they know when their payment has gone through.
Select the relevant skill from the published collection rather than loading every workflow into the task.
Read the instructions and supporting references. Confirm that they fit your project and the work you authorized.
Let the agent inspect the existing integration and follow the current Studio contracts for the change.
Run the appropriate checks and tests. A skill guides the work; it does not replace verification.
Build around the offer
Lead with the gift, make the price obvious, and keep the path to payment short. Here’s a page outline from your holiday brief.
Here’s the shopping flow: choose a mug, review the total, then pay with Inttegro Checkout. Your server will confirm the payment.
Public and reusable
The eight developer skills are published on skills.sh and maintained in the public Inttegro AI repository. Use the documented installation method for your agent, or review and copy the complete skill folder into a supported location.
The plugin bundles developer guidance with authenticated merchant workflows and specialist agents. Choose standalone skills when you need implementation knowledge; add a merchant connection when the task needs access to an Inttegro account.
Start the day with the bigger picture
Sales are up 20%, and Studio mugs brought in half of the week’s revenue. They’re a strong candidate for your next featured offer.
Oct 12–18, 2026 · UTC · Compared with Oct 5–11
Start with a Buy link you can share with customers. Add Checkout when you want buyers to pay from your own website.
Before you get started
No. The developer skills are public instructions and references. An account and appropriate credentials are needed when your application or connected agent performs authenticated Inttegro operations.
No. A skill tells a coding agent how to approach a task. MCP tools let a connected client request Inttegro data or supported actions. They can work together, but installing a skill does not grant account access.
The standalone public collection contains the eight developer skills. Operational workflows, such as handling an order or refund, are bundled separately in the Inttegro plugin and use an authenticated merchant connection.
Start with an Inttegro account
Create your account for free, then connect the tools that fit your workflow. Payment fees and account requirements still apply.