Skip to main content

Build an integration with an agent

An Inttegro-connected agent can guide the architecture conversation, give your coding agent a concrete implementation brief, and check whether the result is ready for an end-to-end test. The workflow is read-only and never asks for API keys, customer records, or source-code uploads.

Start the guided design

Ask the agent:

Design our Inttegro integration. Take me through the decisions, including whether to use an official SDK and whether to use Inttegro Checkout. When we are done, give my coding agent exact implementation steps, initial API operations, canonical Studio links, and an end-to-end test plan.

The agent calls design_integration. A client that supports MCP form elicitation presents four choices:

  1. Primary goal: hosted checkout, custom checkout, orders and invoices, catalog and buy links, customer messaging, or a broader commerce workflow.
  2. Trusted server runtime: TypeScript, Go, Python, PHP, Ruby, Java, .NET, or another runtime.
  3. SDK preference: official SDK or direct HTTPS.
  4. Checkout approach: Inttegro Checkout, custom checkout, or no checkout in the initial workflow.

Clients without form elicitation can pass the same typed choices directly. The tool is stateless: all decisions travel in the tool request or the MCP input response, so the workflow behaves consistently across compatible harnesses.

What the plan contains

The result includes:

  • the selected architecture and recommended path;
  • an SDK install command when the selected runtime has one;
  • the smallest initial set of Inttegro API operations;
  • ordered implementation steps;
  • explicit idempotency, secret-handling, timeout, retry, and state-verification rules;
  • an end-to-end test plan using disposable fixtures;
  • canonical Studio documentation links; and
  • one self-contained agent_brief that can drive a coding task.

The plan does not invent undocumented request fields. Your coding agent should use the linked Studio pages as the contract source and keep INTTEGRO_API_KEY in trusted server infrastructure.

Ask for a focused guide

Use get_integration_guide when the architecture is already known and the agent needs one focused sequence:

  • authentication
  • hosted_checkout
  • custom_checkout
  • orders_and_invoices
  • catalog_and_buy_links
  • customer_messaging
  • idempotency
  • testing

For example:

Give my coding agent the hosted checkout guide. Include the authoritative state-verification step and canonical documentation links.

Check readiness

After implementation, ask:

Check whether our hosted Inttegro Checkout integration is ready for an end-to-end test. The API key is server-side, idempotency keys and error handling are implemented, order lookup verifies state, and success and cancellation return paths are configured.

check_integration_readiness reports each control as pass, fail, or not_applicable, then returns blockers and the exact end-to-end test sequence. It evaluates declared architecture controls; it does not receive secrets or inspect a private repository.

Important boundary

These tools help an agent design and verify an integration plan. They do not create API keys, deploy code, inspect private source, or prove a production integration by themselves. Run the returned tests against a disposable Inttegro application and verify authoritative resource state before production rollout.

Continue with Authentication, Inttegro SDKs, Accept payment with Inttegro Checkout, or the complete MCP tool catalog.