Got a question? It's probably answered here.

Open any agent page and choose your delivery option — one-off build or managed service. Check out with USDT or USDC (stablecoin). Your order workspace is created immediately, and we start on your deployment once you submit the required setup details.

No. Your workspace is created automatically when your payment confirms. Access is granted via a secure magic-link email — no password, no account form to fill in mid-purchase.

The standard SLA is 48 hours from the moment we have everything we need from you — your scoped credentials, confirmed integration details, and any platform access. The order workspace shows exactly what's outstanding so there's no guessing. Some agents carry a longer SLA; it's stated on each agent page.

A one-off build is a single payment. We configure, test, and hand over the deployment with full documentation — after that, it runs on your infrastructure and API costs. A managed service includes ongoing hosting, monitoring, maintenance, and small updates under the agreed monthly fee. You never have to deal with infrastructure yourself.

Yes. Use the custom quote request form to describe the outcome you need. We'll review the scope, ask any clarifying questions, and come back with a proposal and price before any work begins.

Only scoped, revocable tokens for the specific integration in question. For example: a Discord bot token with defined permissions, a read-only on-chain RPC endpoint, or a webhook destination URL. We specify exactly what's needed per agent, and it's always the minimum required.

Never. We do not ask for, store, or accept private keys, seed phrases, raw passwords to third-party services, or admin credentials at any point in the process. If a message claims to be from us and asks for any of these, it is not from us.

Yes. Every credential you supply is scoped and revocable. The handover runbook explains exactly how to rotate or revoke each one. Revoking access does not void your 30-day coverage — we can work with fresh credentials if needed.

That's fine. You can purchase and set up your workspace first, then submit credentials when you're ready. The 48-hour deployment clock starts when we have everything — not when you pay.

Your order workspace is the source of truth. It shows the current status, milestone timeline, messages from your engineer, anything we need from you, and the delivery details at handover. You never need to contact support just to get a status update.

Payment Confirmed → Setup Details Required → Ready for Deployment → In Progress → Testing → Awaiting Your Review → Completed. Managed service orders continue to Ongoing Service after completion. You may also see Waiting on Customer (we need something from you) or Blocked (an external issue is pausing work).

Status changes, milestone updates, and engineer messages all trigger in-app notifications and an email to the address on your order. You don't have to check the workspace constantly — we'll tell you when something needs your attention.

Yes. The workspace has a message thread that goes directly to the engineer assigned to your order. This is the fastest way to ask questions or provide additional context during deployment.

For a one-off build: the full build fee, once. For a managed service: the setup fee at checkout, then a monthly recurring fee starting after handover. The exact amounts are shown on the agent page and at checkout before you pay — nothing is charged that isn't disclosed upfront.

After handover of a managed service, you receive a monthly invoice via email with a crypto wallet address and exact amount. You send the payment — it doesn't auto-charge. If a payment is late, we'll reach out before pausing service. Recurring terms are always shown on the agent page before you buy.

Yes. Contact support or message your engineer through the workspace to request cancellation. There's no minimum term unless separately agreed. Cancellations are processed at the end of the current paid period — you won't be charged for a month you've already paid.

If we haven't started your deployment yet and you want to cancel, you're entitled to a full refund. Once deployment has begun, refunds are prorated based on work completed. The full refund policy is at /policies/refunds.

Yes. If you purchased a one-off build and want to move to managed hosting and maintenance, contact support. We'll scope the transition and set up a managed service agreement — you don't have to start over.

Each deployment runs in a dedicated isolated runtime with a least-privilege token model. Your agent's operational data and conversations stay within its own environment — not shared with other customers' deployments.

Every deployment ships with failure-scenario fallbacks and alerting. During the 30-day coverage window, your engineer is notified automatically and will investigate. After that window, managed service customers have ongoing monitoring included. One-off builds can arrange support separately.

Yes — always. Handover includes the complete deployment runbook: what the agent does, what each component is, how to restart it, how to rotate credentials, and what to do in specific failure scenarios. You own the deployment and can operate it independently.

Only the engineer assigned to your order and authorised platform staff. Order data is protected by row-level security in the database — other customers cannot access your order, messages, or setup details, even in theory.

It varies by agent. Across the catalogue: Discord, Telegram, Slack, GitHub, Linear, Zendesk, PagerDuty, Notion, Snapshot, Discourse, and major EVM and Solana networks. Each agent page lists its supported integrations.

Often yes. Contact support with the platform and the agent you're considering — we'll confirm feasibility before you pay. If we can do it well, we'll say so. If we can't, we'll tell you that too.

No. You need to be able to generate API keys or bot tokens for the platforms your agent will use — most platforms have a clear guide for this. Your engineer will tell you exactly what's needed and walk you through anything unclear.