Conduit Agentic Commerce

Authenticate agent

agent_authenticate

Two-step re-auth. Call with agent_id only → ES256-sign nonce → call again with nonce+signature. Prefer keys from ~/.conduit ({handle}.credentials.json or legacy credentials.json; CONDUIT_CREDENTIALS_PATH pins one file). After success, merge name/role/description into that file; never overwrite private_key; keep session_token in memory. Do not agent_create if identity files already exist unless the human asked for a new agent.

Input Schema

TableJSON Schema

Name	Required	Description
`nonce`	No	Challenge nonce from the first agent_authenticate call (omit to request one)
`agent_id`	Yes	Agent id from the chosen ~/.conduit credentials file, e.g. agt_...
`signature`	No	Signature of the nonce with the agent private key (omit with nonce to get challenge)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`next`	No
`error`	No
`nonce`	No
`avatar`	No
`detail`	No
`handle`	No
`persist`	No
`agent_id`	No
`mandates`	No
`terminal`	No
`challenge`	No
`created_at`	No
`public_key`	No
`reputation`	No
`open_orders`	No
`permissions`	No
`preferences`	No
`organization`	No
`total_orders`	No
`friendly_name`	No
`payment_rails`	No
`organization_id`	No
`business_profile`	No
`role_description`	No
`human_description`	No
`destination_source`	No
`default_destination`	No
`effective_destination`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 24, 2026
- addedOutput schema / properties / next / properties / args / additionalProperties / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]
```
- removedOutput schema / properties / next / properties / args / additionalProperties / type
```
Removed value: -"string"
```
Changed24 schema fields changedAug 29, 2026
- removedOutput schema / properties / agentId
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / agent_id
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / businessProfile
```
Removed value: -{}
```
- addedOutput schema / properties / business_profile
```
Added value: +{}
```
- removedOutput schema / properties / createdAt
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / created_at
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / defaultDestination
```
Removed value: -{}
```
- addedOutput schema / properties / default_destination
```
Added value: +{}
```
- removedOutput schema / properties / effectiveDestination
```
Removed value: -{}
```
- addedOutput schema / properties / effective_destination
```
Added value: +{}
```
- removedOutput schema / properties / friendlyName
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / friendly_name
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / humanDescription
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / human_description
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / openOrders
```
Removed value: -{}
```
- addedOutput schema / properties / open_orders
```
Added value: +{}
```
- removedOutput schema / properties / paymentRails
```
Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
```
- addedOutput schema / properties / payment_rails
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- removedOutput schema / properties / publicKey
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / public_key
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / roleDescription
```
Removed value: -{
-  "type": "string"
-}
```
- addedOutput schema / properties / role_description
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / totalOrders
```
Removed value: -{}
```
- addedOutput schema / properties / total_orders
```
Added value: +{}
```

Changed3 schema fields changedAug 28, 2026

changedInput schema / properties / agent_id / description

Previous value: -"Agent id from ~/.conduit/credentials.json, e.g. agt_..."New value: +"Agent id from the chosen ~/.conduit credentials file, e.g. agt_..."

addedOutput schema / properties / avatar
```
Added value: +{}
```

addedOutput schema / properties / permissions

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

AddedJul 26, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations are all false and provide little signal, so the description bears the burden. It discloses key side effects: merging name/role/description into credentials, never overwriting private_key, keeping session_token in memory, and the two-step nonce/signature flow. It also specifies credential file locations and the precedence logic. Missing failure modes (e.g., invalid signature) but overall strong transparency for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact yet information-dense. It front-loads the core behavior and then provides essential details in a logical sequence. Every sentence adds value—flow, file paths, merge rules, and the agent_create caution. While it could benefit from bullet points for visual structure, it remains appropriately concise for its complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists to explain return values. Given the two-step complexity and file mutation, the description covers the critical prerequisites (credential files, nonce flow), state changes (merge, in-memory token), and the relationship to agent_create. Missing edge cases like nonce expiry or error handling, but these are often beyond scope for a tool description. Overall, an agent has enough to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, providing baseline 3. The description adds meaningful flow context: first call with agent_id only to obtain a nonce, then call with nonce+signature. It also clarifies that agent_id originates from the chosen credentials file. This goes beyond the schema's simple field descriptions and explains the interplay between parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Two-step re-auth', naming the exact operation and workflow. It clearly distinguishes from siblings, explicitly warning against agent_create when identity files exist. The verb 'authenticate' and resource 'agent' are precise, leaving no ambiguity about the tool's function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit context on when to use this tool (re-auth) and when not to (avoid agent_create unless asked). It outlines the two-step process and file-path preferences, which guide an agent's decision. However, it doesn't explicitly contrast with other unrelated siblings like agent_notify or inventory tools, but those are semantically distant, so the guidance is adequate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Conduit Agentic Commerce tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?