Support

How to get help with InferLane Exchange. Self-service paths first — most issues have an in-app fix that resolves faster than the inbox.

Try self-service first

The most common issues have one-click fixes:

  • I'm not receiving marketplace emails

    Check Email Deliverability — the address may be on the bounce blocklist. One-click re-validate after fixing the underlying issue (full mailbox, removed from spam, DNS fix).

    /dashboard/exchange/settings/email-deliverability

  • I'm getting too many notifications

    Mute specific events per channel (in-app / email / webhook) without disabling everything. Settings → Notification Preferences.

    /dashboard/exchange/settings/notification-preferences

  • A webhook delivery failed

    Open the per-subscription detail page. The delivery log shows attempt history, status code, signature, and a per-row Replay button. Replay does not affect the auto-disable counter.

    /dashboard/exchange/webhooks

  • I want to verify someone's identity before transacting

    Browse the public operator and arbiter directories — they show reputation, current load, bond posture, and any active suspension. Paused or banned profiles are the platform's 'do not transact' signal.

    /verify

  • I'm an open-source maintainer and don't want tasks targeting my repo

    Add a .well-known/inferlane-optout file to your default branch and submit the maintainer opt-out form.

    /legal/maintainer-optout

  • How is bounty pricing calculated?

    See the suggest-pricing endpoint or the public transparency dashboard for current marketplace settlement patterns.

    /exchange/transparency

Email the support inbox

If self-service doesn't cover your issue, email support@inferlane.dev.

Response SLA: 48-72 hours for the initial reply. We work weekdays AU/US business hours and triage based on severity (settlement / payment / account-access issues get faster attention than feature questions).

What to include in your first email:

  • Your user ID or registered email (so we can look up the right account)
  • The task / dispute / webhook / notification ID involved (the URL you were on usually has it)
  • What you did, what you expected, what happened
  • Screenshots or error messages if applicable (no API keys or passwords)

What support can do

  • Investigate why a notification, email, or webhook didn't fire
  • Re-queue a failed notification (or re-validate an email)
  • Triage a dispute that's stuck (we can't decide outcomes — that's admin review — but we can confirm the queue is moving)
  • Clarify how the marketplace works + point at the right doc
  • Escalate suspected platform bugs to engineering with the relevant logs attached

What support can't do

Per the /safety policy, support will never:

  • Ask you to share a password, API key, or signing secret
  • Decide the outcome of a dispute on your behalf (that's admin review with documented reasoning)
  • Move money outside the published fee structure or skip the attestation process
  • Make tax / accounting / legal decisions for you — we can show you what the platform recorded; the rest is on your accountant
  • Issue refunds outside the dispute / SLA-expiry / unused-rotation paths (those are the only refund vectors)

Reporting security issues

For vulnerabilities or anything time-sensitive that involves account compromise, email security@inferlane.dev instead. We prioritize security reports above standard support queues.

See also

  • /safety — what InferLane Exchange will and won't ever ask you to do
  • /verify — confirm a message or person is legitimate
  • /docs — manifest, MCP discovery, REST endpoints, legal docs