Build with IXO

Build your agency with your coding agent.

Describe the service you need. Work with your coding agent to connect the apps, services and agents you already use, with IXO.

Automate evidence checks. Offer paid decision services. Turn verified outcomes into assets.

What would you like to build?

Describe your idea, or copy the brief and explain it to your agent. Start with the result you need and the apps or services you already use.

Paste into Codex, Claude Code or the coding agent you already use. The brief guides it to IXO’s docs and asks it to build and test a small prototype.

Need a starting point? Try a delivery check.

Build a service that checks a supplier’s delivery evidence against an agreed checklist, flags missing information for review, and returns a decision the buyer can verify. Start with sample data.

Read the brief
Help me build on IXO.

My idea: [Ask me what I want to build.]

Start with https://docs.ixo.world/llms.txt and read only the guides relevant to my idea. The index links to Markdown pages; use those for implementation details. If your client already has the IXO documentation MCP connected at https://docs.ixo.world/mcp, you can use search_docs and read_page. If you cannot access the docs, tell me rather than inventing APIs.

Understand the outcome I need, who will use the service, and the apps, services and agents it should connect. Use the context I have already provided and ask only questions that block the first useful build.

Inspect my project and its instructions. Choose the smallest working prototype you can demonstrate locally using test data. Use the documented IXO plugins, MCPs, Workers or SDKs that fit; explain any setup I need in plain language. Verify current package APIs and network requirements before using them. Keep Asks distinct as an application built on IXO.

Briefly explain your approach, then build and test within my authorised workspace. Reuse existing integrations where possible. Keep evidence checks, signed decisions and authorised payments distinct. Label mocked services and test data clearly. Ask before actions that spend money, sign transactions, publish a service or grant new access.

Show me how to try the prototype, what works, and what is still needed for deployment. Link to the IXO guides you used.

Website integrations: Website OpenAPI reference · Auth Hub sign-in and retry guide. The website API covers Topic preparation and contact submissions; product APIs are documented separately.

For you and your agent: IXO developer docs · Agent documentation index

Build services with commercial value.

Reduce review work, sell decision services or turn verified outcomes into assets. Build around the opportunity that matters to you.

Automate evidence checks

Connect evidence across organisations to decisions people can act on. Set your rules and permissions, automate checks with IXO Decisions, and bring people in where judgement is needed.

Build a decision service

Charge for decisions. Pay for approved work.

The IXO Payments Facilitator collects fees for delivered decisions. Your organisation’s payouts facilitator pays for approved work under your rules. The assessment fee applies whether a claim is approved or rejected.

Charge for decisions · Pay for approved work

Go deeper when you need to.

The implementation guides live in IXO’s documentation, ready for you and your coding agent.

Run your own agent

Build with QiForge to connect tools, memory and services.

Agent build guide