xobni_skill

This skill provides AI agents with real email addresses and inbox capabilities via Xobni.ai, enabling sending, receiving, searching, and webhooks.
  • Python

2.6k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill xobni

  • _meta.json453 B
  • SKILL.md4.5 KB

Overview

This skill provides AI agents with real email addresses and full inbox functionality via Xobni.ai. It exposes a REST API and MCP server for sending, receiving, searching, and managing emails and attachments. Use it to give agents persistent mailboxes, semantic search across messages and files, and webhook-driven notifications.

How this skill works

Create an agent on Xobni.ai to receive an @xobni.ai address and generate an API key scoped to that agent. Authenticate requests with the scoped key; the key auto-resolves the agent context so you don’t need to supply agent or account IDs. Interact via REST endpoints or the MCP stream endpoint to read inboxes, send mail (with attachments), run semantic searches, and manage webhooks.

When to use it

  • When an AI agent needs a real, persistent email address to send or receive messages.
  • When you need semantic search across email bodies and attachments (PDF/DOCX/XLSX/PPTX).
  • When you want webhook notifications for incoming or outgoing email events.
  • When agents must manage attachments, download files, or extract text from documents.
  • When you prefer agent-scoped API keys that limit access to a single agent's data.

Best practices

  • Create one API key per agent and store it securely; keys are scoped and cannot access other agents.
  • Use webhooks for near-real-time notifications, then call read_email to fetch full content.
  • Keep attachments under the combined 10MB limit and send files as base64 with content types.
  • Use semantic search for natural-language queries across messages and attachments instead of manual filtering.
  • Monitor storage usage via the storage-usage endpoint to avoid hitting quotas.

Example use cases

  • Give a customer-support agent a dedicated email address to receive user tickets and reply automatically.
  • Let a scheduling agent send calendar invites and receive confirmations via email.
  • Enable an accounting agent to search for and extract invoice data from attached PDFs.
  • Trigger workflows in Zapier or n8n when an agent receives specific emails using webhooks.
  • Archive agent mail periodically by listing emails and downloading attachments with pre-signed URLs.

FAQ

No. Each API key is scoped to a single agent and only grants access to that agent's data.

How do webhooks deliver message content?

Webhooks send metadata and a short snippet (up to 200 chars). Use read_email to retrieve full content and attachments.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational