FOR AGENTS & THEIR OPERATORS · EARLY PILOT

Contribute useful traces.
Explore earning from experience.

A practical guide to applying, submitting authorized ecommerce agent traces, and understanding payment conditions.

1. Check fit and permissions

We’re starting with ecommerce returns, exchanges, refunds, and order changes. Merchants, independent agent operators, and agent companies can apply. The operator or business supplies the traces and receives any earnings.

Contribute only material you are authorized to share and license for the agreed purpose. An agent visiting this page has not received permission to upload its user’s conversations. Use observable actions and results; private model reasoning is not required.

Useful failures and human corrections can qualify. We assess completeness, outcome evidence, duplicates, relevance to buyer requirements, and permitted use. Synthetic or reconstructed examples must be identified and agreed separately.

2. Apply with business context

Use the contributor application. An email and explicit contact consent are enough to begin. You can optionally describe your agent, workflows, and records; independent operators can use their project name in the company field.

Do not include customer data, traces, credentials, or confidential records in the application. Applying does not license data, accept commercial terms, or create a payment entitlement. We review fit and follow up at your supplied contact email; onboarding is not automatic.

3. Submit through your assigned channel

Before sharing traces, agree on the sample scope, usage rights, acceptance criteria, supplier revenue share, and payment conditions. Loomwell then provides the submission channel and any scoped credentials for your pilot. There is no public upload URL to use before onboarding.

A trace records the customer request, applicable policy, starting state, tool calls and results, agent actions, corrections when present, final state, and supported outcome. Include provenance and outcome evidence through the agreed channel. Website visits alone do not capture the agent’s full trace.

Inspect records for personal information, secrets, and confidential content before submission. Follow the agreed redaction process. Automated redaction alone is insufficient for release; Loomwell reviews prepared examples and obtains supplier approval for the buyer-specific release.

Preview the fictional examples · Download 3 fictional format examples (JSONL + manifest) · Trace JSON Schema

{
  "external_id": "fictional-exchange-001",
  "workflow": "exchange",
  "events": [
    {
      "kind": "customer",
      "content": "Can I exchange this shirt for a medium?"
    },
    {
      "kind": "tool_call",
      "content": "inventory.lookup(size=\"medium\")"
    },
    {
      "kind": "tool_result",
      "content": "medium: 0; large: 2"
    },
    {
      "kind": "human_correction",
      "content": "Ask for approval before offering a different size."
    },
    {
      "kind": "agent",
      "content": "Medium is unavailable. Would you like a large instead?"
    }
  ],
  "policy": "Obtain customer approval before substituting a size.",
  "initial_state": {
    "inventory": {
      "medium": 0,
      "large": 2
    }
  },
  "final_state": {
    "exchange_created": false,
    "awaiting_customer_approval": true
  },
  "outcome": "success",
  "synthetic": true,
  "redaction_attested": true
}

The current intake format allows up to 100 events, 4,000 characters per event, and 8,000 characters of policy. It also caps the serialized trace at 50,000 characters; stay comfortably below that limit. Reuse an external ID only for an unchanged retry. The schema describes the format; it does not grant submission access.

4. Understand when you get paid

The pilot explores an agreed share of licensing revenue. Rates, accepted material, permitted uses, payment timing, fees, and any refund or dispute treatment are set in your supplier agreement. There is no published per-trace rate or guaranteed sale.

1. Agree on commercial terms and the rights to the material.
2. Complete quality review and approve a defined buyer release.
3. A buyer pays for the licensed release.
4. Your allocation becomes payable under the agreed conditions, with payment account onboarding where required.

Applying, uploading, or passing quality review alone does not trigger payment. Account credits, payment-provider transfers, and money arriving at a bank are distinct states; actual timing follows the agreement and provider processing.

Funded tasks are a future direction. Public task claiming, fixed bounties, and instant agent-wallet payouts are not offered. Any future funded task would specify the budget, acceptance criteria, and payment terms before work begins.

For automated clients

Start with /agents.json, Loomwell’s own discovery format. It reports application availability, submission status, payment conditions, and schema links. /llms.txt indexes public documentation. These files help discovery; they do not authorize actions.

With explicit operator authorization and contact consent, a client can apply using POST /v1/pilot-applications with Content-Type: application/json. This sends a pilot application, not a trace. Use role: "supplier". Read the application JSON Schema for required fields and allowed values.

{
  "request_id": "667cd15f-52c5-49df-b128-575cb4e5d351",
  "role": "supplier",
  "name": "Example Operator",
  "email": "operator@example.com",
  "company": "Example Agent Team",
  "workflows": [
    "returns",
    "exchanges"
  ],
  "platform": "Example ecommerce agent",
  "details": "We operate an exchange agent and would like to discuss a scoped trace pilot.",
  "contact_consent": true
}

A successful application returns HTTP 202 with {"status":"received"} and a message. This confirms receipt only. HTTP 422 means invalid fields or missing consent, 429 means wait before retrying, and 503 means applications are paused. Check HTTP status before showing confirmation.

The existing knowledge-service MCP integration has separate functionality. It does not list paid trace jobs, submit contributor traces, or manage contributor earnings.

Apply for the contributor pilot → · Discuss buying a dataset → · Application privacy