The Machine Agent Identity Protocol (MAIP) ships with integrations that bring agent identity, receipts, and trust scoring into your existing workflows. Each integration generates cryptographic receipts automatically, so every action has a verifiable audit trail.
Prerequisites: You need a Truthlocks account with an API key and at least one registered agent. See the machine identity guide to register your first agent.
Browse and filter all available integrations on the Integrations Hub. You can search by category, framework, or platform to find the right connector for your stack.
A sidebar panel for browsing receipts, generating receipts from your editor, and viewing trust data. Install it from the Visual Studio Marketplace.What it does:
Browse and search MAIP receipts from the sidebar
Generate receipts for code changes directly from the editor
View agent trust scores and receipt chains
Installation:
Open VS Code and go to the Extensions view (Ctrl+Shift+X / Cmd+Shift+X).
Search for “Truthlocks MAIP”.
Click Install.
Alternatively, install from the command line:
code --install-extension truthlocks.maip-vscode
After installing, open the MAIP sidebar panel and enter your API key and agent ID to connect.
A Lua-native plugin for Neovim that integrates MAIP receipts, agent management, and trust scores into your editor. Includes Telescope integration for searching receipts and a statusline component for displaying agent status.Setup with lazy.nvim:
Telescope integration:Use :MaipSearch or call require("telescope").extensions.maip.receipts() to open a fuzzy-finder over your receipts. Results show the receipt ID, type, and timestamp. Press <CR> to view full details in a split buffer.Statusline component:Add the agent trust score to your statusline by calling the provider function. For example, with lualine:
The component displays the agent ID and current trust score, and updates automatically when you create receipts or refresh trust data.Auto-receipt on save:Enable automatic receipt generation whenever you write a buffer by setting auto_receipt = true in your setup call:
A Model Context Protocol server that exposes 20 tools, 4 resources, and 3 prompts for AI assistants to interact with the MAIP platform. Use this to give your AI coding assistants direct access to agent registration, receipt generation, and trust score queries.Example configuration:
Slash commands let your team query receipts, trust scores, and agent status directly from Slack. Interactive Block Kit layouts display receipt details, risk summaries, and dashboards inline.Available commands:
Issue and comment events in Linear automatically create MAIP receipts. You can verify receipts and post trust scores as comments, with bidirectional sync between Linear and the MAIP platform.
Automatically creates Receipts, Agents, and Trust Scores databases in your Notion workspace. Syncs receipts incrementally, generates audit report pages, and updates Notion in real time via webhooks.
Automatically generate MAIP receipts for commits, pull requests, releases, CI runs, and build artifacts. Verification results appear as GitHub Check Runs with trust score badges on your PRs.Example workflow:
Python connectors that generate a MAIP receipt for every AI model call, capturing token counts, cost estimates, and SHA-256 content hashes. Prompts and responses are hashed — not stored — for privacy.
from truthlocks_langchain import TruthlocksCallbackcallback = TruthlocksCallback( api_key="tl_live_your_api_key", agent_id="maip-agent:01JXXXX")# Every LLM call now generates a MAIP receiptchain.invoke({"input": "Summarize this document"}, config={"callbacks": [callback]})
A multi-backend event streaming gateway that generates MAIP receipts for messages flowing through your data pipelines. Use it when you need receipt-backed audit trails for event-driven architectures.Supported backends:
Backend
Description
Kafka
Apache Kafka message receipts with batched flushing
AWS EventBridge
Publish and subscribe to EventBridge events with receipts
AWS Kinesis
Kinesis stream records with receipt generation
NATS
NATS messaging with receipt-backed delivery
Redis Streams
Redis Streams pub/sub with automatic receipts
Each backend includes built-in deduplication, retry middleware, and operational metrics. Configure the gateway to connect to one or more backends and every message automatically gets a MAIP data-flow receipt.Example configuration:
from truthlocks_streaming import StreamingGatewaygateway = StreamingGateway( api_key="tl_live_your_api_key", agent_id="maip-agent:01JXXXX", backends=[ { "type": "kafka", "brokers": ["localhost:9092"], "topic": "events", "batch_size": 100, }, { "type": "redis", "url": "redis://localhost:6379", "stream": "receipts", }, ],)# Every message published through the gateway generates a MAIP data-flow receiptgateway.publish("events", {"action": "user.login", "user_id": "u_123"})
You can run multiple backends simultaneously. The gateway deduplicates messages across backends using content hashes, retries failed deliveries with exponential backoff, and exposes Prometheus-compatible metrics at /metrics.
If you only need Kafka receipts without the multi-backend gateway, use the standalone Kafka connector instead.
Python plugin that generates cryptographic receipts for every MLflow model run, providing provenance proof for your ML experiments.
import mlflowfrom truthlocks_mlflow import TruthlocksPluginmlflow.set_tracking_uri("http://localhost:5000")TruthlocksPlugin.enable(api_key="tl_live_your_api_key", agent_id="maip-agent:01JXXXX")with mlflow.start_run(): # Your training code — a receipt is created automatically mlflow.log_metric("accuracy", 0.95)
Python plugin for creating MAIP receipts on DVC data versioning operations. Each dvc push or dvc pull generates a receipt linking the data version to your agent identity.
Python plugin for generating receipts on Delta Lake table operations. Tracks table writes, schema changes, and compaction events with cryptographic provenance.
You can run MAIP integration services as Docker containers instead of installing them locally. Official images are available for the CLI, MCP Server, event streaming gateway, and Slack integration.
Use Docker Compose to start all MAIP services together. This is the fastest way to get started with self-hosted MAIP integrations for local development and testing.Create a docker-compose.yml file: