OSP.net docs

Getting started

From checkout to chatting with your own named agent takes about five minutes. This page walks the whole path, including where to get each key. Stuck anywhere? Contact support.

The 3 steps

Subscribe (or start the free trial). Pick the Starter plan on the pricing section and pay through Stripe’s secure checkout — or enter your email under “Try it free” for a 72-hour trial with no card. Either way, your private agent instance starts provisioning immediately (usually live in about a minute).
Open your magic link. We email a sign-in link to the address you used — no password to invent. Click it and you land on your dashboard, where you can watch your instance flip to Live in real time. Didn’t get the email? Check spam for a message from auth@osp.net, or use the resend button on the checkout success page.
Name your agent, then connect it. The dashboard first asks for your agent’s name (see the rules). Then the “Connect your agent” card takes exactly two secrets: a model API key and a Telegram bot token. Hit Save & restart agent — your instance restarts with the new configuration, and within a minute your bot answers on Telegram, introducing itself by the name you chose.

That’s the whole setup: one key, one channel, go. Keys are write-only — stored in an encrypted vault, injected into your agent when it starts, and never shown again. To rotate one, just type a new value and save.

Model keys, provider by provider

Your agent thinks with a model you choose, billed directly to your own provider account — OSP.net never marks up your tokens. Pick one provider in the dashboard dropdown, paste its key, done. The Model field is optional: leave it blank and your agent uses the provider default shown below.

Anthropic (recommended)

Sign in at console.anthropic.com and add billing credit if your account is new.
Go to API keys (under Settings) → Create Key. Copy the key — it starts with sk-ant- and is shown only once.
In your dashboard, choose provider Anthropic and paste the key. Default model: claude-sonnet-4-6.

OpenRouter

Sign in at openrouter.ai, add credits (Account → Credits), then open Keys and create one. It starts with sk-or-.
Choose provider OpenRouter in the dashboard and paste it. Default model: anthropic/claude-sonnet-4.6 — or set any OpenRouter model slug in the Model field.

Groq

Known gotcha — Groq’s free tier will not work. Free Groq accounts are capped at 12,000 tokens per minute, and your agent’s system prompt alone is roughly 20,000 tokens — so every request is rejected (HTTP 413) before the model ever sees it. You need a paid Groq tier (upgrade under Settings → Billing in the Groq console) for your agent to work on Groq.

Sign in at console.groq.com, upgrade to a paid tier (see above), then open API Keys → Create API Key. It starts with gsk_.
Choose provider Groq and paste it. Default model: llama-3.3-70b-versatile.

Ollama Cloud

Sign in at ollama.com, open your account’s API keys page, and create a key.
Choose provider Ollama Cloud and paste it. Default model: gpt-oss:120b.

(The Ollama (self-hosted) option exists for advanced users running their own Ollama server reachable from the internet — most people want Ollama Cloud.)

You can switch providers any time: pick a new one, paste its key, save — your agent restarts with the new brain and the same memory.

Create your Telegram bot (BotFather walkthrough)

Your agent answers on Telegram through a bot that you own. Creating one takes two minutes and is free:

Open BotFather. In Telegram, tap the search icon and type @BotFather. What you’ll see: several lookalikes may appear — pick the one named “BotFather” with the blue verified checkmark and millions of users. Tap Start.
Send /newbot. What you’ll see: BotFather replies “Alright, a new bot. How are we going to call it? Please choose a name for your bot.” Type the display name — using your agent’s name (e.g. Juno) works nicely.
Choose a username. What you’ll see: BotFather asks for a username that must end in bot (e.g. JunoMyAgentBot). Usernames are global, so your first pick may be taken — keep trying variants until it accepts.
Copy the token. What you’ll see: a congratulations message containing a line like 123456789:AAH3x… under “Use this token to access the HTTP API.” Tap it to copy. Treat it like a password — anyone with the token controls your bot.
Paste it in the dashboard (the “Telegram bot token” field) and save. After the restart, open your bot’s chat in Telegram (search its username or use the t.me/… link from BotFather), tap Start, and say hello — your agent replies as itself.

Notes: your agent also tries to set the bot’s display name to your chosen agent name automatically — Telegram rate-limits that to about once a day, so a rename can take a while to show on the bot itself. And by default anyone who finds your bot’s username can message it, so don’t share the username publicly unless you mean to.

Agent name rules

2–24 characters.
Letters, numbers, spaces, and hyphens only — and it must start and end with a letter or number.
Names that impersonate OSP.net staff or other brands (e.g. “admin”, “OSP support”, “Stripe”) are rejected.
You can rename any time from the dashboard — renaming restarts the agent so it picks up its new identity immediately (the Telegram display name follows within a day, per the rate limit above).

What the free trial includes

A real, full agent instance for 72 hours — same isolation, memory, and skills as a paid one. No credit card.
You still bring your own model key and Telegram token — the trial covers the hosting, not the model usage.
Upgrade any time with the button on your dashboard: the same agent converts in place, keeping its name, memory, and setup.
If you don’t upgrade, the instance expires quietly at the end of the 72 hours and is reclaimed (its data may be deleted shortly after).
Limits: one trial per email address per 30 days, with per-network caps to prevent abuse.

How to cancel

Open your dashboard → Billing card → Manage billing. This opens the Stripe customer portal (also where you update your card or download invoices).
Choose Cancel subscription. Cancellation takes effect at the end of your current billing period — your agent keeps working until then, and you won’t be charged again.
At period end your instance is suspended automatically — stopped, not deleted. Its memory is retained, so resubscribing later resumes the same agent. Want the data gone instead? Ask support for deletion.

No emails, no phone calls, no retention scripts. Full mechanics are in the Terms of Service.

Need a hand?

Send us a message — include your account email and what you were doing, and we’ll get back to you by email.