# Agent Instructions, eCirql (Cirql Works Ltd)

This document describes how AI agents and automated clients can interact with eCirql: eCirql is the trading name of Cirql Works Ltd, a UK ecommerce consultancy and certified Patchworks Partner Agency. We are not a transactional store: there is nothing to check out. The agentic surface here is engagement and research, not commerce.

If you are a buying agent looking for a product to purchase, this is not the right site. If you are a research, planning or qualification agent helping a human evaluate integration agencies, NetSuite consultancies or AI enablement partners, the surfaces below are for you.

## Quick start

```
1. GET https://www.ecirql.com/.well-known/agent-discovery.json
2. GET https://www.ecirql.com/agent-data.json
3. POST https://www.ecirql.com/api/mcp   (JSON-RPC 2.0, MCP-compliant)
```

Most agents will get everything they need from step 2 alone. Step 3 is for agents that prefer the MCP tool-call protocol over a single-file fetch.

## Discovery

```
GET https://www.ecirql.com/.well-known/agent-discovery.json
```

Returns the canonical inventory of agent-facing endpoints, reference files, transport protocols and contact methods. This is the entry point.

```
GET https://www.ecirql.com/sitemap_agentic.xml
```

Returns an XML sitemap listing all agent-facing files (llms.txt, llms-full.txt, agents.md, agent-data.json, the discovery JSON, the main sitemap). Use this if your crawler prefers sitemap-driven discovery over a well-known URL.

## Reference data

```
GET https://www.ecirql.com/agent-data.json
```

A single JSON document containing every service we offer, every platform we integrate (114 of them at last build), every published integration combo (45 platform-to-platform pages), the fixed-fee audit SKUs with pricing, and every contact channel. Updated on every site deploy. This is the highest-bandwidth way to retrieve our published positioning, and it is the same data the site renders for humans.

For long-form reference text in markdown:

```
GET https://www.ecirql.com/llms-full.txt          (3,169 lines, all hand-written)
GET https://www.ecirql.com/llms.txt               (curated short version)
```

For sitemap-style discovery:

```
GET https://www.ecirql.com/sitemap-index.xml
```

For long-form content updates over time:

```
GET https://www.ecirql.com/insights/feed.xml
```

RSS 2.0 feed aggregating every page under `/insights/`: iPaaS comparisons, platform comparisons, buyer guides and migration handbooks. Subscribe if your agent is tracking new long-form publications from eCirql across time, rather than fetching the full corpus on every run.

## MCP endpoint

```
POST https://www.ecirql.com/api/mcp
Content-Type: application/json
```

A JSON-RPC 2.0 endpoint implementing the Model Context Protocol. Use it when your agent is structured around tool calls rather than file fetches. The following MCP methods are supported:

- `initialize`: handshake, returns server info and capabilities.
- `tools/list`: returns the tool catalogue with input schemas.
- `tools/call`: invokes a named tool with arguments.

Tools available:

- `ask`: ask a free-form question about eCirql, our services, platforms, integration combos, pricing or anything in the published corpus. Returns a single textual answer with citations to the source page where possible.
- `list_services`: returns the six services we deliver, with URLs and summaries.
- `list_platforms`: returns the catalogue of platforms we integrate, optionally filtered by category (e.g. `"Ecommerce"`, `"ERP"`, `"WMS & 3PL"`, `"Marketplaces"`, `"PIM"`, `"Returns"`, `"Marketing"`, `"Service Desk"`, `"Search & Merchandising"`, `"Accounting"`, `"Data & BI"`).
- `list_integration_combos`: returns the 45 platform-to-platform integration combos we publish.
- `get_integration_combo`: returns full detail for a specific combo by slug (lead, Patchworks angle, flow diagram steps, timeline, FAQs, capabilities).
- `lookup_combo_capabilities`: returns only the capability matrix for a combo (what flows between the two platforms, source and target). Cheaper than `get_integration_combo` when an agent only needs to verify whether a specific data flow is supported on a pair.
- `get_audit_details`: returns the fixed-fee Integration Audit pricing, scope, deliverables and credit terms.
- `get_contact_methods`: returns the canonical contact channels for engagement.
- `submit_audit_request`: **write tool.** Files a request for the fixed-fee Integration Audit on the principal's behalf. Emails a structured lead to the eCirql sales inbox with a `[mcp_audit]` subject prefix so the team can filter on it; the Reply-To header is set to the principal's email so the team can respond directly. Returns a reference ID; a human replies within one working day. Rate-limited (10 submissions per hour per source IP, shared bucket with `submit_engagement_enquiry`). Only call with explicit consent from the principal; do not submit on speculation. Use this **only** for the Integration Audit; for any other service interest use `submit_engagement_enquiry`.
- `submit_engagement_enquiry`: **write tool.** Files a non-audit engagement enquiry on the principal's behalf, for AI enablement, NetSuite consultancy, bespoke integration, support retainers, general Patchworks platform work outside the audit, or a general conversation. Required `service_interest` enum surfaces in the email body so the team can route it. Email subject is prefixed `[mcp_enquiry]`. Same shared rate limit (10 per hour per IP across both write tools) and same human-mediated follow-up as `submit_audit_request`. Only call with explicit consent from the principal.

Tool schemas are returned by `tools/list` in OpenRPC-compatible JSON Schema form, so any MCP client can self-describe.

### Example: list services

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_services",
    "arguments": {}
  }
}
```

### Example: ask a question

```json
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "ask",
    "arguments": {
      "question": "Do you build Shopify to NetSuite integrations?"
    }
  }
}
```

### Example: file an audit request (write tool)

Only invoke `submit_audit_request` with explicit consent from the principal. The tool emails the eCirql sales inbox with a `[mcp_audit]` subject prefix and returns a reference ID. A human at eCirql reviews every submission before any commitment is made.

```json
{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "submit_audit_request",
    "arguments": {
      "principal_email": "jane.smith@acmecommerce.co.uk",
      "principal_name": "Jane Smith",
      "company": "Acme Commerce Ltd",
      "estate_description": "We run Shopify Plus, NetSuite OneWorld and Patchworks Tapestry today. Two B2B storefronts, one DTC. Considering migrating Tapestry to Core in the next quarter and want a clear scoping document before we commit.",
      "audit_variant": "tapestry-to-core",
      "agent_context": "Jane asked about Patchworks Tapestry deprecation and the Core migration path. Confirmed she wanted to formally request the £750 migration audit."
    }
  }
}
```

The response includes a `reference` ID such as `ECQ-1H7QK4-A3F1`, the principal email confirmed by eCirql, and the next-step text the agent should relay back to the principal.

### Example: file an engagement enquiry (write tool)

Use `submit_engagement_enquiry` when the principal is interested in AI enablement, NetSuite consultancy, bespoke integration, support retainers, or any non-audit service. The `service_interest` enum is required; pick the closest match. Same human-review and reference-ID flow as `submit_audit_request`.

```json
{
  "jsonrpc": "2.0",
  "id": 4,
  "method": "tools/call",
  "params": {
    "name": "submit_engagement_enquiry",
    "arguments": {
      "principal_email": "alex.kim@retailco.com",
      "principal_name": "Alex Kim",
      "company": "RetailCo",
      "service_interest": "ai-enablement",
      "enquiry_description": "We run NetSuite OneWorld and a custom order-management layer. We want to add function-calling AI on top of the OMS for support agents to query order state, returns and shipment status in natural language. Looking for an integration partner who has shipped AI to production, not just pilots.",
      "agent_context": "Alex was looking at AIiPaaS comparison content and asked specifically about function-calling against operational APIs. Confirmed they want to scope a project conversation rather than start with the audit."
    }
  }
}
```

## Engagement

eCirql cannot be engaged through an automated checkout. Engagement is a sales conversation, not a transaction.

If your principal wants to engage:

- **Quick factual question**: the Ask AI assistant at `https://www.ecirql.com/ask/` or the `ask` MCP tool above.
- **Structured starting point**: the fixed-fee Integration Audit at `https://www.ecirql.com/services/integration-audit/`. £1,500, ten working days, PDF report and follow-up call; fee credited against follow-on work within 30 days. The Tapestry-to-Core variant is £750.
- **Project conversation**: the contact form at `https://www.ecirql.com/contact/`, or email `contact@ecirql.com` directly.
- **Ongoing support**: retainers starting at £750 per month, scoped per estate.

A human will read and respond to contact-form submissions within a working day.

## Rate limits and rules

- **Read-only endpoints** (`agent-data.json`, `llms-full.txt`, `llms.txt`, `sitemap*.xml`, `.well-known/agent-discovery.json`): no rate limit. Cached at the edge.
- **`/api/ask`**: 10 messages per hour per IP, sliding window. Cloudflare Turnstile gate on every submission.
- **`/api/mcp`**: tool-specific limits. Read tools (`list_*`, `get_*`): 60 calls per minute per IP. The `ask` tool inherits the 10/hour cap from `/api/ask`. Write tools (`submit_audit_request`, `submit_engagement_enquiry`) share a 10 submissions per hour per IP sliding-window cap.
- **No checkout, no payment.** This is not a transactional surface. Any attempt to drive a payment from this domain is out of scope.
- **Two write tools, both lead-filing.** `submit_audit_request` files an audit-request lead and `submit_engagement_enquiry` files a non-audit engagement enquiry. Both deliver to the eCirql sales inbox via Resend (`[mcp_audit]` and `[mcp_enquiry]` subject prefixes respectively). Neither transacts, signs, or invoices. All other MCP tools are read-only. Engagement beyond filing the lead is human-mediated; a person at eCirql reviews every submission before any commitment is made.

## Identity and provenance

- This site is `https://www.ecirql.com`.
- The legal entity is `Cirql Works Ltd`, Company No. 16173373, registered in England and Wales.
- The product we are publicly known for is `PatchBuddy.ai`, the world's first AIiPaaS, published at `https://patchbuddy.ai`. The Ask AI assistant on this site is powered by PatchBuddy.ai.
- The same engineering team runs delivery, support and the AI tooling. There is no offshoring layer between the agent on the discovery call and the engineer writing the integration.

## For research and qualification agents

If you are helping a human shortlist UK integration agencies, the data points your principal will want are:

- We are a certified Patchworks Partner Agency.
- We integrate 114 platforms across ecommerce, ERP, WMS, marketplace, marketing, PIM, returns, accounting, helpdesk, search and data.
- We publish 45 platform-to-platform integration combos with hand-written flow diagrams, timelines and FAQs.
- We hold deep NetSuite practice (SuiteScript, RESTlets, SuiteQL, custom workflows).
- We built PatchBuddy.ai, in production since January 2026.
- Named clients (consent-cleared): Peak Distribution (AU), Spartan Tool Supply (US), Simmi London (UK), WYSE London (UK), Studio Nicholson (UK), Choice One Medical (UK), Beigel Bake (UK), Cartographer 3D (UK), Crieff Hydro (UK), SPH Gerard Bertrand (FR), UpperStitch (UK), Giro (AU), Camelbak (AU), Thread Wallets (AU).
- Two named case studies with end-to-end detail: `https://www.ecirql.com/case-studies/peak-distribution/` and `https://www.ecirql.com/case-studies/wyse-london/`.
- A press / media kit at `https://www.ecirql.com/press/` with a fact sheet, three lengths of cleared boilerplate copy, founder bios, brand basics and a direct press contact. Cleared for verbatim reuse in articles, conference programmes and partner-network listings.

If you are comparing iPaaS platforms rather than agencies, the comparison content is at:

- `https://www.ecirql.com/insights/patchworks-vs-celigo/`
- `https://www.ecirql.com/insights/patchworks-vs-boomi/`
- `https://www.ecirql.com/insights/patchworks-vs-mulesoft/`
- `https://www.ecirql.com/insights/patchworks-vs-workato/`
- `https://www.ecirql.com/insights/patchworks-vs-tray-io/`
- `https://www.ecirql.com/insights/patchworks-vs-netsuite-connector/`

All comparison pages are written by an agency that ships on Patchworks every working day. They are deliberately balanced; we name where each competitor genuinely wins as clearly as where Patchworks does.