MCP & AI Agent Integration

Pidj
automation.

12 AI agent actions for Pidj — callable from any MCP-compatible runtime, Claude, Cursor, or Cerebral OS workflow. Use Pidj to organize files, generate documents, and manage permissions programmatically. Full governance, audit trail, and dry-run safety on every execution.

No credit card required
Live in production environments
<200ms median execution
Dry-run before production
Execution trace
live
12
actions
100%
governed
<200ms
latency
12
AI agent actions
5
Read operations
7
Write operations
2
High-risk actions (approval gated)
Files & Documents Pidj is a Files & Documents integration — use it to automate file storage, sharing, and document management from any AI agent or MCP-compatible runtime.
Actions

What you can do
with Pidj.

Every action below is available as an MCP tool and a verb in Cerebral OS — callable from any AI agent, Claude, Cursor, Windsurf, or your own runtime via the BYOA API. All executions are governed, audited, and dry-run safe.

Get Profile
pidj:get_profile
Fetch a single customer profile by ID with all attributes and computed fields.
Read Low risk
Get Segment
pidj:get_segment
Fetch details for a specific customer segment including criteria and member count.
Read Low risk
List Events
pidj:list_events
List events for a specific customer profile with optional filtering.
Read Low risk
List Profiles
pidj:list_profiles
Search and list customer profiles with filtering options.
Read Low risk
List Segments
pidj:list_segments
List all customer segments with optional filtering and search.
Read Low risk
Add Profile To Segment
pidj:add_profile_to_segment
Add a customer profile to a segment (works for static segments only).
Write Medium risk
Create Profile
pidj:create_profile
Create a new customer profile with optional attributes and tags.
Write Medium risk
Create Segment
pidj:create_segment
Create a new customer segment with optional dynamic criteria.
Write Medium risk
Delete Profile
pidj:delete_profile
Permanently delete a customer profile and all associated data.
Write High risk
Remove Profile From Segment
pidj:remove_profile_from_segment
Remove a customer profile from a segment (works for static segments only).
Write High risk
Track Event
pidj:track_event
Track a custom event for a customer profile with optional properties.
Write Medium risk
Update Profile
pidj:update_profile
Update an existing customer profile with new data, attributes, or tags.
Write Medium risk
MCP & Runtime API

Call Pidj
from any AI agent.

Any AI agent — Claude, Cursor, LangChain, AutoGen, or your own — can call Pidj actions through the Cerebral OS Runtime API. Governance, credentials, and audit trail fire automatically.

pidj:get_profile READ
# Call via Runtime API
curl
-X POST \
  "https://api.cerebralos.com/v1/runtime/actions/run"
  -H "X-API-Key: YOUR_KEY" \
  -d '{
    "verb": "pidj:get_profile",
    "args": {},
    "execution_id": "agent-001"
  }'
pidj:add_profile_to_segment WRITE
# Dry-run first — no production risk
curl
-X POST \
  "https://api.cerebralos.com/v1/runtime/actions/run"
  -H "X-API-Key: YOUR_KEY" \
  -d '{
    "verb": "pidj:add_profile_to_segment",
    "args": {},
    "execution_id": "agent-001",
    "metadata": {"dryRun": true}
  }'
Get your Runtime API key at app.cerebralos.com/signup — 1,000 free executions, no credit card required.
AI agent examples

What your AI agent
can do with Pidj.

Real patterns your AI agent can execute via MCP or the Runtime API. Every action governed, dry-run safe, and fully audited.

Trigger
AI agent needs Pidj data
Call pidj:get_profile via MCP or Runtime API
AI processes result and takes next action
Full execution logged to audit trail automatically
Trigger
Workflow needs to write to Pidj
Dry-run validates pidj:add_profile_to_segment before execution
Approval gate fires if risk level is high
Action executes with full governance — logged, audited, reversible
Trigger
File or document event
Process with AI
Route for approval
Notify team
How it works

Every Pidj action
governed end-to-end.

Cerebral OS isn't a connector. It's the execution layer that sits in front of Pidj — adding governance, dry-run safety, and a full audit trail to every operation.

Governance first
Every verb carries a risk classification. High-risk writes require explicit approval gates before they execute in production.
Dry-run safe
Simulate any Pidj action before it touches production. See exactly what would happen before a single real call is made.
Immutable audit trail
Every Pidj action is logged — what ran, what changed, who approved it, when it happened. Full history on every verb, forever.
Connect with

Pidj works best
alongside these.

Build multi-step workflows that connect Pidj to the rest of your stack. All governed. All audited.

Pidj integration

Start free.
No credit card required.

Start free with 1,000 runs — no credit card required. Connect Pidj in minutes, dry-run every action before it touches production, full audit trail on everything.

Start free — 1,000 runs Browse all integrations →