Get your service connected

Which services

• SaaS that people use for work — ERP, e-commerce, accounting, tax invoices, logistics, marketing — anything an AI tool can read or act on.
• Services with an official API come first. We do not use unofficial methods such as screen scraping or reverse engineering.
• If you already run your own MCP server, we can look at attaching it as a remote MCP.
• No API yet? You can still propose — we will talk about what scope could be opened first.

What we need

• A public REST API or OAuth — the auth method (OAuth 2.0, API key, …) and a link to the docs.
• A test account for development (a sandbox is even better).
• Rate limits — calls per minute/day and concurrency limits.
• Read/write scope — by default we open read-only first and let the user turn writes on.

How it works

1. Proposal — send it to the email below.
2. Review and reply — we look at the docs and scope and get back to you.
3. Trial integration — we build a read-focused bridge against a test account and check it together.
4. Launch — the service moves from “coming soon” to “available” for users.

Our principles

• Customer data does not pass through Tera servers. The app talks to your service directly from the user’s PC. Tera servers only handle license checks, plugin downloads and update distribution.
• Calls are made only with the user’s own permissions, and writes stay blocked until the user turns them on.
• We never work around unofficial APIs or terms of service.