Email, SMS & AI under your brand.
One API connects your site to every channel — sending through your own verified domain and A2P-registered number, not a shared relay. We run the infrastructure. You build on it.
curl https://tegomarketing.com/api/v1/email/send \
-H "Authorization: Bearer tego_k_…" \
-H "Content-Type: application/json" \
-d '{
"to": "athlete@example.com",
"subject": "You're registered",
"html": "<p>See you at the start line.</p>"
}'
# → { "ok": true, "messageId": "a1b2c3…" }Your site, your product. Call one API instead of stitching together four vendors.
Every send goes out as you — your domain, your number — so deliverability and replies stay yours.
We run domains, A2P registration, wallets, and metering. You never touch the plumbing.
Four channels, one key
Discovery
AI (structured)
Events & workflows
Contacts & events
CRM sync
Email finder
Cold outreach
Marketing calendar
SMS
Documents
Reports
Webhook deliveries
Insights
Brand
Email drafts
Social drafts
Financials
Keys that describe themselves
One call returns the channels a key can use and the identity it sends as — so your app configures itself instead of hard-coding what’s enabled.
{
"account": "Sorted Luxe",
"channels": {
"email": { "enabled": true, "from": "hello@sortedluxe.com" },
"sms": { "enabled": false, "reason": "No active number on this account." },
"ai": { "enabled": true }
},
"scopes": ["email:send", "ai:generate"]
}From key to first send in minutes
Authenticate
Authorization: Bearer tego_k_…Send under your brand
from address and number are derived server-side from your verified domain and A2P number — callers can’t spoof identity.Everything is metered
curl https://tegomarketing.com/api/v1/ai/object \
-H "Authorization: Bearer tego_k_…" \
-H "Content-Type: application/json" \
-d '{
"messages": [
{ "role": "user", "content": "Extract the race name and date." }
],
"schema": {
"type": "object",
"properties": {
"race": { "type": "string" },
"date": { "type": "string" }
},
"required": ["race", "date"]
}
}'
# → { "object": { "race": "Lake George Triathlon", "date": "2026-09-05" } }curl https://tegomarketing.com/api/v1/sms/send \
-H "Authorization: Bearer tego_k_…" \
-H "Content-Type: application/json" \
-d '{
"to": "+15551234567",
"body": "Alpha Win: packet pickup 7–8:30am. Reply STOP to opt out."
}'
# The from-number is your own A2P-registered number — server-derived,
# never spoofable. Requires an approved A2P number on the account.curl https://tegomarketing.com/api/v1/events \
-H "Authorization: Bearer tego_k_…" \
-H "Content-Type: application/json" \
-d '{
"name": "web_order",
"data": { "items": "2x Stefan sticker", "total": "$4.00", "how": "PICKUP" }
}'
# → { "ok": true, "name": "web_order" } (202 — recorded, not yet acted on)
#
# Build a workflow in the portal with an "External event" trigger named
# web_order, and every field in `data` is available to its steps as
# {{data.items}}, {{data.total}}, {{data.how}}. Change what the email says,
# who it goes to, or add an SMS — no deploy of your app.Your AI, working your account.
TEGO runs an MCP server. Point Claude, Cursor or any MCP client at it with your key, and it can read your pipeline, contacts, campaign results, monthly reports, website traffic, Google search and reviews, tickets, calendar, invoices and estimates, and your brand and products. With write scopes it can also update the records and draft invoices, emails, social posts in your brand, and review replies for us to approve. It never sends, posts, schedules, publishes or launches anything, and it never takes a payment: that stays in your portal.
One key, one account
Scopes decide the tools
crm:read sees the pipeline tools; reports:read adds campaign results and monthly reports. Results are paged, every call is logged.Writes are retry-safe
crm:write, contacts:write and the other write scopes add tools that create and update records. Creates take an externalId, so an assistant that retries gets the first record back instead of a second one.claude mcp add --transport http tego https://www.tegomarketing.com/api/mcp \
--header "Authorization: Bearer tego_k_…"Run it in your terminal. Start Claude Code and type /mcp: tego shows as connected.
// .cursor/mcp.json
{
"mcpServers": {
"tego": {
"url": "https://www.tegomarketing.com/api/mcp",
"headers": { "Authorization": "Bearer tego_k_…" }
}
}
}Save it as .cursor/mcp.json in your project, or paste it under Cursor Settings, then MCP. Reload Cursor: tego appears in the MCP list with a green dot.
// claude_desktop_config.json
{
"mcpServers": {
"tego": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://www.tegomarketing.com/api/mcp",
"--header", "Authorization: Bearer ${TEGO_KEY}"],
"env": { "TEGO_KEY": "tego_k_…" }
}
}
}In Claude Desktop open Settings, then Developer, then Edit Config. Paste it into claude_desktop_config.json. If the file already has mcpServers, add the tego entry inside it. Save and restart Claude Desktop. It needs Node.js installed for npx.
Scoped keys, no shared secrets
- Bearer keys prefixed tego_k_, encrypted at rest (AES-256-GCM).
- Per-scope grants — a key gets only what it needs.
- Account-bound keys can't be redirected to another client by the request.
- Sends are rate limited per account — a 429 carries Retry-After. Retries are not deduplicated, so key your own idempotency.
Predictable JSON
Every error is JSON with a stable code and a human message. Standard statuses: 401 unauthorized, 400 validation, 403 not enabled, 404 not found.
{
"error": {
"code": "SMS_NOT_ENABLED",
"message": "No A2P-approved number on this account."
}
}Metered, not subscribed.
Every channel bills to your account, with usage visible in your Billing tab. No seat fees. No per-contact tax.
A per-account credit wallet with optional auto-recharge. You set the rate; sends draw down and reconcile after delivery.
SMS
Same wallet model, charged per segment. Routes through your own A2P number — reply attribution and opt-outs stay yours.
AI
Billed on tokens per request, metered to your account. Run Claude on TEGO's key so no model secret ever leaves the platform.