Omentir v2 is a simple idea rebuilt from the ground up: outbound should not feel like operating five disconnected tools.
Most teams do not need more dashboards. They need a system that understands who they sell to, finds the right people, writes outreach with context, respects safe sending limits, and gives founders or sales teams a clear way to turn interest into pipeline.
That is what v2 is built around. Omentir is no longer just a LinkedIn outreach assistant. It is becoming the outbound layer for humans, AI agents, and the tools they already use.
New Pricing
We are making pricing simpler. The goal is not to create confusing usage math. The goal is to make it easy to start small, prove the channel, and scale once the pipeline is working.
The headline change is a brand new tier. We are introducing Basic at $29/month, and at the same time we are upgrading the existing Startup plan so it gives you a lot more for the same price.
Here is what changed. Earlier there was no $29 option. The only paid plan was Startup at $59/month, and it included a single LinkedIn account. Now that same $59 Startup plan includes three LinkedIn accounts, and we have added a much cheaper entry point: the new $29 Basic plan for a single LinkedIn account. So you can start outbound for less, and the plan you already knew now does three times the work.

The Basic plan is built for solo founders who want one focused outbound motion: one LinkedIn account, one AI agent, one campaign, and up to 50 leads per day.
The Startup plan is for small teams that want more room to run: up to three LinkedIn accounts, three AI agents, unlimited leads, unlimited campaigns, and AI automated campaigns.
For larger teams, Enterprise remains custom. That includes unlimited LinkedIn accounts, unlimited AI agents, managed campaigns, SSO, and dedicated support.
You can see the current plan details on the Omentir pricing page.
Agent API
The biggest shift in v2 is that Omentir is becoming programmable. With Agent API, trusted tools can read workspace context, inspect your product profile, create discovery agents, list leads, create campaigns, run automation dry-runs, and review conversations through REST endpoints.
That matters because outbound does not live in one place anymore. Some teams work from CRMs. Some use internal scripts. Some use AI agents. Some want a founder-facing dashboard, while others want everything controlled from their own workflow.
Agent API gives those teams a clean way to build on top of Omentir without bypassing the safety layer. Campaigns still respect workspace readiness, LinkedIn connection state, pacing rules, and daily limits.

You can create a workspace-scoped key from API keys. From there, integrations can call a few core endpoints:
GET /api/agent/v1/contextto check workspace readiness and available resources.GET /api/agent/v1/leadsto inspect discovered prospects before a campaign uses them.POST /api/agent/v1/campaignsto create a draft or active campaign against an approved lead group.
For the full technical surface, use the live OpenAPI schema at /api/agent/v1/openapi.json or the agent guide at /agents.md.
API principle
The API is not a shortcut around Omentir's safety model. It is a programmable path through the same workspace checks, campaign rules, and pacing controls used by the product.
Connectors for Agentic Workflows
v2 also introduces connectors for agentic workflows. Omentir now exposes an MCP server, so tools like Claude, ChatGPT, Cursor, Hermes, OpenClaw, and custom agents can connect to Omentir with a workspace-scoped API key.
The setup is intentionally lightweight: create an Omentir key, paste the MCP URL into the agent's connector settings, and let the client discover the available tools. The agent gets structured capabilities instead of raw account access.

Once connected, an agent can help with the full outbound workflow: understand the workspace, check the product profile, create a lead discovery agent, review leads, draft or launch campaigns, run dry-run checks, and inspect replies.
Technically, the connector gives an agent a typed tool surface instead of a vague browser session. A few useful tools look like this:
omentir_get_contextomentir_create_campaignomentir_list_conversationsThe dashboard is still there for people who want a clean product experience. But now Omentir can also work wherever your operator, founder, developer, or AI agent already lives.
For setup details, read the Omentir MCP server guide.
Why This Matters
Outbound is changing. The old workflow was manual and fragmented: scrape leads in one tool, enrich them in another, write messages somewhere else, upload everything into a sequencer, then hope the campaign does not sound generic.
The next workflow is more fluid. You describe who you sell to. Omentir finds qualified buyers. Your AI agent can inspect the workspace, ask for more context, create campaigns, and monitor replies. Humans stay in control where judgment matters, while repetitive work gets handled by the system.
v2 is our move toward that future. Not more automation for the sake of automation. Better discovery, better outreach, safer execution, and cleaner ways to plug Omentir into the rest of your stack.
What Comes Next
Omentir v2 is built for founders and teams who want outbound to feel less like admin work and more like a repeatable path to customers.
The product is moving in one direction: fewer disconnected steps, more qualified conversations, and a safer way to let agents help with the work that used to slow every outbound team down.
Frequently Asked Questions
Omentir v2 is the next version of Omentir, focused on simpler pricing, programmable outbound through Agent API, and connectors for AI agents.
Omentir now has a Basic plan at $29/month, a Startup plan at $59/month, and custom Enterprise pricing for larger teams that need more accounts, workflows, support, and controls. The idea is to let teams start small and scale only when outbound is working.
Agent API exposes workspace-scoped REST endpoints so trusted tools can read context, inspect leads, create campaigns, run dry-runs, and review conversations without bypassing Omentir's pacing and safety rules.
An Omentir connector lets an AI tool connect to your Omentir workspace through a secure URL and workspace-scoped key. Instead of copying data between tools, the agent can call approved Omentir tools directly.
MCP is best when an AI agent should discover and call tools directly. REST API is best when a developer wants to wire Omentir into scripts, internal systems, or custom backend workflows.
No. Agent actions still pass through Omentir's workspace checks, campaign state, daily quotas, LinkedIn connection requirements, and dry-run paths. The connector gives agents access, not unlimited control.


