Invite Beta Support

Direct support for invite beta buyers, sellers, and operators.

Support is human and direct during invite beta. It is best-effort support, not an SLA, but it should be enough for real usage and fast issue triage.

Email support@dragonfly-api.com Status page Beta support matrix

Response target

Best effort within one business day

Invite beta support covers onboarding blockers, unsupported-mode confusion, and market governance questions.

We do not promise procurement paperwork, dedicated TAM coverage, or enterprise uptime commitments in this phase.

If the status page shows an ongoing incident, check there first before opening a duplicate report.

Include these details

Help us triage quickly

The account email you registered with
Which client or SDK you are using
Request IDs or timestamps for the failing call
The model name and endpoint path involved
Whether the issue is buyer, seller, or operator side

Buyer Self-Service

Common blockers before you email support

Invite beta buyers should be able to resolve the first layer of issues without guessing where to go next. These links map directly to the onboarding, wallet, and support-matrix flows in the product.

Verification email did not arrive

Most buyer onboarding stalls are still email verification. Check the guide, resend the link, then contact support if the backlog keeps growing.

Check spam and promotions folders first.
Use the verification guide to resend the latest link.
If the link expired or never arrived after one hour, email support with your account email.

Open verification guide

Top-up succeeded but balance did not update

Invite beta top-ups should land in Wallet quickly. If you paid and still see insufficient credits, use the wallet page before filing a report.

Open Wallet and confirm the latest transaction exists.
Refresh the page and confirm the balance changed.
If the payment exists but balance is still wrong, send the payment time and account email to support.

Open wallet

You can log in but still cannot create a key

Buyer key creation is blocked until email verification and credits are both ready. The buyer setup page tells you which step is incomplete.

Open Get Started to see the blocked step.
Verify email first, then confirm you still have credits.
If both are ready and key creation still fails, include the error code in your support email.

Open buyer setup

Your client or mode is not supported

Invite beta does not promise every OpenAI-adjacent mode. Check the support matrix before assuming the failure is on your account.

Confirm the endpoint and SDK you are using.
Check whether the mode is inside the current invite beta support matrix.
If the mode is supported and still failing, include the request ID and model name when contacting support.

Open support matrix

Failure Recovery

When the first request fails, recover by error type instead of retrying blindly.

Verify your email first

Key creation stays locked until email verification completes.

Open verification

Regenerate or re-copy the key

401s usually mean the request is using an old key, a partial copy, or the wrong prefix.

Open buyer keys

Switch to a supported starter model

Use the live starter model instead of cached or outdated examples.

Open quick start

Top up credits

The request path is valid, but the wallet has no spendable balance.

Open wallet

Retry with a fallback route

No eligible seller channel was healthy enough for the current constraints.

Open playground

Refresh and retry

The gateway returned HTML or a mismatched surface instead of JSON.

Open support

Buyer issues

Email verification, credits, key creation, and supported client setup.

Seller issues

Listing admission, reserve ledger questions, penalties, and risk actions.

Operator issues

Invite beta rollout, daily reviews, and release smoke failures.

Escalate Fast

Email support immediately if any of these happen

You completed payment but balance or transactions still look wrong after refresh.
Verification links keep expiring or never arrive for multiple invites.
You already have credits and still get blocked from buyer key creation.
A supported client path fails with request IDs you can share.

Best Contact

Support inbox

Use one email thread per issue so buyer, seller, and operator follow-up does not get mixed together.

Email support@dragonfly-api.com