OpenClaw integration

OpenClaw-style agent stacks want tools that do real work. Omentir supplies hosted MCP and REST tools for product context, lead finders, Steal Customers, leads, schedules, and constrained conversation actions so your agent is not inventing a LinkedIn client from scratch.

Create a workspace API key on the Omentir API keys page. Store it as a secret. Send Authorization: Bearer on MCP or REST calls. Never embed the token in public prompts or git commits. Rotate keys if a runner environment is compromised.

• MCP: https://omentir.com/api/agent/v1/mcp
• REST: https://omentir.com/api/agent/v1
• OpenAPI: https://omentir.com/api/agent/v1/openapi.json
• Guide: https://omentir.com/agents.md

Fetch agents.md first. Call get_context. Refuse to create agents until the human confirms targeting. On empty lead lists, check list_activity before claiming discovery worked. Reply tools only on existing threads with draft approval.

Background agents can loop. Cap retries, require approvals for create and delete, and log every outbound-affecting tool call. Autonomy without an audit trail is how silent targeting drift happens.

OpenClaw is useful when you want an operator that already lives on your machine. That also means a leaked token is a leaked workspace. Rotate the key if the machine is shared, and start with read-only habits: context, stats, lead lists.

When you let it create a finder, give it a file or message with the ICP. Do not ask it to crawl your whole disk for 'ideas.' The workspace should change because you asked, not because the agent got bored.

If you just want to talk to Omentir from a hosted chat app, use Claude, ChatGPT, or Grok. OpenClaw adds a local runtime you have to operate. That is worth it for people who already run it. It is extra surface for everyone else.