Pentatonic
Pentatonic | Agentic Multi-Commerce
https://pentatonic.com/Connect straight to this server’s public endpoint.
https://api.pentatonic.com/api/mcpWe add this server to your workspace, walk through sign-in once, then open Studio with tools ready to run.
Last probed Sep 14, 2026 · api.pentatonic.com
33tools discovered
Showing 25 of 33 from the live probe.
Introspect Schema
Introspect the GraphQL schema to discover all available types, queries, mutations, and fields. Use this FIRST before querying to understand the API structure and available filter fields.
Query Things
Query things (physical items) with optional filters and pagination. Things represent items tracked through lifecycle stages including: manufactured → sold → in_use → captured → identified → valued → listed_for_sale → resold → recycled. Filter by client_id (tenant/organization e.g. 'tes-demo'), current_stage, product_id, holder_id (person/entity holding the item), location_id, etc. Related holder and location data is resolved via graph traversal. Maps to ItemRecord in agentic-commerce.
Get Thing
Get a single thing by ID with full details including holder, location, and status history.
Create Thing
Create a new thing (physical item) to track through its lifecycle. Can optionally create holder and location inline, or reference existing ones by ID. Emits a CREATE event.
Update Thing
Update a thing's attributes. Emits an UPDATE event. Can update holder, location, or add status entries.
Add Thing Status
Add a status entry to a thing's lifecycle history. This is the primary way to track state transitions and attach rich data (condition, value, media, provenance). Status entries form the event history from which current state is derived. Use stages like: captured (item added via wallet), identified (AI identification), valued (price estimate), listed_for_sale, sold, returned, processing, recycled, etc.
Transfer Ownership
Transfer ownership of a thing to a different holder. Updates the thing's top-level holder_id FK and triggers edge_history tracking. Use this instead of manually calling update_thing with holder_id — it's the canonical way to record custody changes. Requires transfer:thing permission.
Change Location
Move a thing to a different location. Updates the thing's top-level location_id FK and triggers edge_history tracking. Use this instead of manually calling update_thing with location_id — it's the canonical way to record location changes. Requires changeLocation:thing permission.
Query Holders
Query holders (customers, warehouses, stores, carriers, processors, manufacturers). Holders are entities that can own or hold things. Maps to Participant in agentic-commerce. Filter by type, name, email, etc.
Get Holder
Get a single holder by ID with full details including things they currently hold.
Create Holder
Create a new holder (customer, warehouse, store, etc.). Returns holder_id for use in thing creation.
Query Locations
Query locations (warehouses, stores, processing centers, distribution centers, customer addresses, etc.). Locations are physical places where things can be at any point in their lifecycle. Filter by type, name, city, etc.
Get Location
Get a single location by ID with full details including things currently at this location.
Create Location
Create a new location (warehouse, store, processing center, etc.). Returns location_id for use in thing creation.
Query Products
Query products (catalog archetypes) with optional filters and pagination. Products represent catalog items that things are instances of. Filter by name, sku, brand, manufacturer, category, tags, etc. Maps to ProductRecord in agentic-commerce.
Get Product
Get a single product by ID or SKU with full details including related things count.
Create Product
Create a new product (catalog archetype). Products define the template for things. Emits a CREATE event.
Update Product
Update a product's attributes. Emits an UPDATE event.
Unique Product Tags
Get all unique tags across products in the organization. Useful for tag selection UIs and filtering.
Query Events
Query the immutable event store with optional filtering and pagination. Events represent all state changes in TES (CREATE, UPDATE, DELETE). Filter by entityId, entityType, eventType, or timestamp range. Returns events in reverse chronological order (newest first).
Event Stats
Get aggregated event statistics including total count, counts by entity type, counts by event type, and activity in the last 24 hours and 7 days.
Conversation Stats
Get conversation analytics: total conversations, messages, searches, clicks, average turns per conversation, search rate, and click-through rate. Use this when asked about chat performance or customer engagement metrics.
Top Search Queries
Get the most common product search queries from chat conversations, with result counts and click-through data. Use this when asked what customers are searching for or looking for.
Conversation Dead Ends
Find conversations that ended without a product click or with failed searches. Identifies three types of dead ends: 'no_search' (messages but AI never searched), 'no_clicks' (searched but customer didn't click any product), 'no_results' (searched but got zero results). Use this when asked about drop-off points, dead ends, or where conversations fail.
Query Conversation Events
Query conversation events (CHAT_TURN, PRODUCT_SEARCH, PRODUCT_CLICK). Provide session_id to get a full conversation transcript. Without session_id, returns recent events matching filters. Use this to drill into specific conversations or browse recent activity.
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Directory coverage for brandsPentatonic | Agentic Multi-Commerce
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
MCPBundles probed 33 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
Pentatonic may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Operate Pentatonic? Verify ownership to take over this directory entry.
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.