Skip to content

Explore Inttegro

Reusable guidance for coding agents

Teach your coding agent how Inttegro works.

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.

ChatGPT

Keep busy checkouts dependable

You: Customers sometimes tap Pay twice. Help me avoid duplicate gift orders.
ChatGPT

Reuse the gift order if a customer taps Pay twice. I’d verify these three cases before the gift campaign.

One purchase, one order

  • Double tap: keep one GHS 780 gift order.
  • Slow response: recover that order instead of creating another.
  • Payment pending: show a waiting message, not a receipt.
You: Review this checkout flow. What could confuse someone buying a gift?

Your flow needs a clearer ending when payment takes longer. Keep the same order and tell the customer you’re checking it.

Keep the customer informed

  • Before payment: show the items and GHS 780 total.
  • While checking: keep the order number visible.
  • After confirmation: show that payment was received.

Eight public skills

Keep platform-specific knowledge close to the task.

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.

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 guidance

Checkout and state synchronization

Use 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 synchronization

Testing and debugging

Use 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 guidance

Upgrades and MCP

Use 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 guidance
Perplexity

Build with the right guidance

You: I’m adding gift orders to my shop. Which Inttegro skills will help?
Perplexity

Use the Checkout skill to build the buying flow, state-sync to check payment, and testing to cover retries before launch.

A dependable gift checkout

Take the customer to payment
inttegro-checkout
Know when it is paid
inttegro-state-sync
Check the complete journey
inttegro-testing
You: Help customers see what happened after they pay for their mugs.

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 clear ending to Checkout

  • Paid: confirm the purchase and show the order number.
  • Pending: explain that payment is still being checked.
  • Unpaid: let them return to the same order to try again.

A focused starting point

Match the skill to the change.

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.
  1. Choose

    Select the relevant skill from the published collection rather than loading every workflow into the task.

  2. Review

    Read the instructions and supporting references. Confirm that they fit your project and the work you authorized.

  3. Apply

    Let the agent inspect the existing integration and follow the current Studio contracts for the change.

  4. Verify

    Run the appropriate checks and tests. A skill guides the work; it does not replace verification.

Gemini

Build around the offer

You: Turn this holiday brief into a page that helps customers buy our mugs.
Gemini

Lead with the gift, make the price obvious, and keep the path to payment short. Here’s a page outline from your holiday brief.

Clayline’s holiday page

  • Headline: A little joy, with every cup.
  • Offer: Studio mug, GHS 160 through December 24.
  • Button: Shop the holiday offer → dedicated Buy link.
You: Help me sell our mugs on the website I’m building in v0.

Here’s the shopping flow: choose a mug, review the total, then pay with Inttegro Checkout. Your server will confirm the payment.

From product page to paid order

  • Product page: Studio mug, GHS 180, quantity selector.
  • Server: create and finalize the order.
  • Confirmation page: show the verified payment result.

Public and reusable

Use the skills on their own or with the plugin.

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.

Claude

Start the day with the bigger picture

You: Give me a quick sales brief before I open the shop.
Claude

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.

Clayline at a glance

Sales
GHS 12,960 · +20%
Paid orders
54 · +20%
Top product
Studio mug · GHS 6,480

Oct 12–18, 2026 · UTC · Compared with Oct 5–11

You: Can I sell my mugs online before I build a full website?

Start with a Buy link you can share with customers. Add Checkout when you want buyers to pay from your own website.

Start selling your way

Share one product
Buy link
Bill a specific order
Hosted invoice
Sell on your website
Inttegro Checkout

Before you get started

A few useful answers.

Do I need an Inttegro account to read or install the skills?

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.

Are skills the same thing as MCP tools?

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.

Do the skills include merchant workflows?

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

Teach your coding agent how Inttegro works.

Create your account for free, then connect the tools that fit your workflow. Payment fees and account requirements still apply.