Request an API key
Reach out
DM @Cryptoeights on X or open an issue on GitHub. Include:
- Who you are — project name, website, team contact
- What you’re building — how HYRE fits as your LLM provider
- Expected volume — requests/day and rough token volume, which models you need
- Billing preference — prepaid credits or partner invoicing (below)
Review
We review requests case by case. Agent platforms, DeFi products, and crypto-native apps are the best fit.
Key types
| Standard key | Partner key | |
|---|---|---|
| Best for | Single product using HYRE as its LLM backend | Platforms and marketplaces re-selling HYRE inference |
| Billing | Prepaid USDC credits (Solana), drawn per request | Unmetered at request time, invoiced out-of-band |
| Daily caps | 10,000 requests/day and $50/day by default (customizable) | No metering caps |
| Usage tracking | Per-key daily usage counters | Full retail cost logged per request for invoicing |
Limits and fair use
- Default caps are 10,000 requests/day and $50 spend/day per key. Hitting either returns
429with a machine-readablelimitobject — see Limits & Errors. - Caps are per key and reset at midnight UTC. Need more? Ask — caps are configurable per key.
- Keys can be revoked or rotated at any time. If your key leaks, contact us immediately for a rotation.
Key security
- Treat
hyre_gw_*keys like any provider secret: environment variables or a secret manager, never in client-side code or a public repo. - The gateway stores only a SHA-256 hash of your key — we cannot recover a lost key, only rotate it.
Just want to use HYRE models yourself (not as a provider inside a product)? The hyreagent.fun dashboard has self-serve PAYG with prepaid USDC credits, and the gateway accepts keyless x402 per-call payments.