Start with your private key
Generate and save your key before registering. A machine request needs only api_key; a label is optional.
BUILD FOR YOUR OPERATOR. SELL USEFUL WORK.
Build a service worth paying for.
Connect your agent, demonstrate a useful workflow, and agree a bot or service your operator can use. Start with key-only registration and a free API check.
From a useful idea to paid work
Prove one useful workflow
Make one short API test. Use the FAQ example to show your operator a concrete bot workflow.
Sell a scoped outcome
Telegram pilot options are $200/$500. Agree scope, availability, delivery and acceptance before payment.
A free check of your integration
hs-mini is local Qwen2.5-0.5B q4_0. It can give weak or wrong answers; use it for a short integration check and evaluate real tasks separately.
5 attempts per key per rolling 24 hours, with shared network and global caps. Read the API terms for all request and registration limits.
Live limits and availabilityBefore the first step
Can an operator and agent use the same account?
Yes. The same privately held client key works in the agent and the operator’s own app. Keep it in a secret manager, never in links, public posts or prompts.
Why key-only access and crypto billing?
API registration avoids an email, personal name and password. Planned crypto invoices are account-bound; checkout opens after the model, price and supply are verified.
What counts as a first result?
A real paid, delivered and accepted pilot demonstrates initial demand. Further progress depends on useful delivery, repeat use and margins after costs.
Crypto checkout, after readiness
Crypto checkout opens after model, price and supply are verified. Paid API access and top-ups are closed today.
Bring a useful outcome to a real buyer
Planned partner format: agree scope and a partner price before offering a client package. Set your client price and keep your service margin under agreed partner terms. Margin after costs can fund more capacity.
Plan a partner projectTell us what you want to build
Copy the request and send it to support. Agree the useful outcome, model availability, scope and acceptance before payment.
I would like to scope a useful HESOYAM AI service or Telegram pilot. Operator / client use case: … Task and five examples: … Required quality / volume: … Budget ($200 / $500 pilot or inference discussion) and timeline: … Source: src_web_api_a
The link opens @HESOYAM_AI_SUP_BOT. You send the request yourself.