@reclaimprotocol/agent 0.1.1 → 0.1.3

package/src/mcp/api/operations.gen.ts

@@ -294,7 +294,7 @@ export const MCP_TOOLS = {
 		}),
 	},
 	"CreateCallbackSubscription": {
-		description: "Register a callback subscription\n\nRegisters a destination for verification results on the organization\nthe presented `OrgToken` resolves to. The body is just `callbackUrl`\nand `events`. At least one subscription must exist for the org before a\nverification session can be created. Delivery is scoped by org: terminal\nresults are encrypted as a compact JWE to the org's encryption\ncredential when set (see `PUT /orgs/{orgId}/credential`), else delivered\nas plaintext.\n",
+		description: "Register a callback subscription\n\nRegisters a destination for verification results on the organization\nthe presented `OrgToken` resolves to. The body is just `callbackUrl`\nand `events`. At least one subscription must exist for the org before a\nverification session can be created. Delivery is scoped by org: terminal\nresults are ECIES-encrypted to the org's eth public key when its\n`canEncryptResult` is enabled (see `PUT /orgs/{orgId}/keypair`), else\ndelivered as plaintext.\n",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -330,11 +330,12 @@ export const MCP_TOOLS = {
 							"maxItems": 12,
 							"items": {
 								"type": "string",
-								"description": "Lifecycle event reported for a verification session. A healthy run\nproceeds through these in order; reading the gaps locates where a\nsession stalled. Session-level terminal events trigger callback\ndelivery; request-level events are progress pings carrying a\n`request_id` in their event data. New values may be added over time;\nclients MUST tolerate unknown values in responses.\n\n- `session_pending`: Session created; awaiting the end-user.\n\n- `verification_client_opened`: The end-user opened the link. Absent ⇒\n  the link was never opened.\n\n- `verification_client_ready`: The client initialized.\n\n- `request_matched`: The target request was captured on the provider\n  site. Absent (after opened) ⇒ the user didn't complete the journey.\n\n- `request_claim_created`: A proof claim was started.\n\n- `request_claim_completed`: A proof claim finished.\n\n- `request_claim_rejected`: A claim was rejected (detail in `eventData`).\n\n- `request_claim_failed`: A claim errored (detail in `eventData`).\n\n- `verification_success`: Terminal — verified. Triggers callback delivery.\n\n- `verification_rejected`: Terminal — rejected (detail in `eventData`).\n\n- `verification_error`: Terminal — errored (detail in `eventData`).\n\n- `session_expired`: `expiresAt` passed before a terminal event.",
+								"description": "Lifecycle event reported for a verification session. A healthy run\nproceeds through these in order; reading the gaps locates where a\nsession stalled. Session-level terminal events trigger callback\ndelivery; provider-/request-level events are progress pings carrying a\n`provider_id` (and `request_id` for request-level ones) in their event\ndata. New values may be added over time; clients MUST tolerate unknown\nvalues in responses.\n\n- `session_pending`: Session created; awaiting the end-user.\n\n- `verification_client_opened`: The end-user opened the link. Absent ⇒\n  the link was never opened.\n\n- `verification_client_ready`: The client initialized.\n\n- `verification_provider_started`: The client began verifying a provider\n  (`provider_id`/`resolved_version`/`ordinal` in `eventData`). One per\n  provider, in run order, for multi-provider sessions.\n\n- `request_matched`: The target request was captured on the provider\n  site. Absent (after opened) ⇒ the user didn't complete the journey.\n\n- `request_claim_created`: A proof claim was started.\n\n- `request_claim_completed`: A proof claim finished.\n\n- `request_claim_rejected`: A claim was rejected (detail in `eventData`).\n\n- `request_claim_failed`: A claim errored (detail in `eventData`).\n\n- `verification_success`: Terminal — verified. Triggers callback delivery.\n\n- `verification_rejected`: Terminal — rejected (detail in `eventData`).\n\n- `verification_error`: Terminal — errored (detail in `eventData`).\n\n- `session_expired`: `expiresAt` passed before a terminal event.",
 								"enum": [
 									"session_pending",
 									"verification_client_opened",
 									"verification_client_ready",
+									"verification_provider_started",
 									"request_matched",
 									"request_claim_created",
 									"request_claim_completed",
@@ -378,14 +379,26 @@ export const MCP_TOOLS = {
 				"body": {
 					"type": "object",
 					"additionalProperties": false,
+					"description": "Body for `POST /orgs`. Explicitly-created orgs must declare their Ethereum (secp256k1) encryption public key — it identifies the org and, when `canEncryptResult` is enabled, encrypts delivered results.",
 					"required": [
-						"name"
+						"name",
+						"publicKey"
 					],
 					"properties": {
 						"name": {
 							"type": "string",
 							"minLength": 1,
 							"maxLength": 200
+						},
+						"publicKey": {
+							"type": "string",
+							"description": "The org's eth public key, uncompressed hex (`0x04` + 128 hex) — the eth-native form wallets/ethers emit. The matching private key never leaves the consumer.",
+							"pattern": "^0x04[0-9a-fA-F]{128}$"
+						},
+						"canEncryptResult": {
+							"type": "boolean",
+							"description": "When true, terminal results are ECIES-encrypted to this key; when false (the default), they are delivered as plaintext.",
+							"default": false
 						}
 					}
 				}
@@ -442,11 +455,12 @@ export const MCP_TOOLS = {
 							"maxItems": 12,
 							"items": {
 								"type": "string",
-								"description": "Lifecycle event reported for a verification session. A healthy run\nproceeds through these in order; reading the gaps locates where a\nsession stalled. Session-level terminal events trigger callback\ndelivery; request-level events are progress pings carrying a\n`request_id` in their event data. New values may be added over time;\nclients MUST tolerate unknown values in responses.\n\n- `session_pending`: Session created; awaiting the end-user.\n\n- `verification_client_opened`: The end-user opened the link. Absent ⇒\n  the link was never opened.\n\n- `verification_client_ready`: The client initialized.\n\n- `request_matched`: The target request was captured on the provider\n  site. Absent (after opened) ⇒ the user didn't complete the journey.\n\n- `request_claim_created`: A proof claim was started.\n\n- `request_claim_completed`: A proof claim finished.\n\n- `request_claim_rejected`: A claim was rejected (detail in `eventData`).\n\n- `request_claim_failed`: A claim errored (detail in `eventData`).\n\n- `verification_success`: Terminal — verified. Triggers callback delivery.\n\n- `verification_rejected`: Terminal — rejected (detail in `eventData`).\n\n- `verification_error`: Terminal — errored (detail in `eventData`).\n\n- `session_expired`: `expiresAt` passed before a terminal event.",
+								"description": "Lifecycle event reported for a verification session. A healthy run\nproceeds through these in order; reading the gaps locates where a\nsession stalled. Session-level terminal events trigger callback\ndelivery; provider-/request-level events are progress pings carrying a\n`provider_id` (and `request_id` for request-level ones) in their event\ndata. New values may be added over time; clients MUST tolerate unknown\nvalues in responses.\n\n- `session_pending`: Session created; awaiting the end-user.\n\n- `verification_client_opened`: The end-user opened the link. Absent ⇒\n  the link was never opened.\n\n- `verification_client_ready`: The client initialized.\n\n- `verification_provider_started`: The client began verifying a provider\n  (`provider_id`/`resolved_version`/`ordinal` in `eventData`). One per\n  provider, in run order, for multi-provider sessions.\n\n- `request_matched`: The target request was captured on the provider\n  site. Absent (after opened) ⇒ the user didn't complete the journey.\n\n- `request_claim_created`: A proof claim was started.\n\n- `request_claim_completed`: A proof claim finished.\n\n- `request_claim_rejected`: A claim was rejected (detail in `eventData`).\n\n- `request_claim_failed`: A claim errored (detail in `eventData`).\n\n- `verification_success`: Terminal — verified. Triggers callback delivery.\n\n- `verification_rejected`: Terminal — rejected (detail in `eventData`).\n\n- `verification_error`: Terminal — errored (detail in `eventData`).\n\n- `session_expired`: `expiresAt` passed before a terminal event.",
 								"enum": [
 									"session_pending",
 									"verification_client_opened",
 									"verification_client_ready",
+									"verification_provider_started",
 									"request_matched",
 									"request_claim_created",
 									"request_claim_completed",
@@ -753,9 +767,9 @@ export const MCP_TOOLS = {
 											}
 										}
 									},
-									"matches": {
+									"responseMatches": {
 										"type": "array",
-										"description": "A list of match conditions for the response.",
+										"description": "Conditions the (redacted) response must satisfy for the proof to be valid. Each runs against the union of the portions revealed by `responseRedactions` (or the whole response when there are none). Mirrors attestor-core `responseMatches`.",
 										"minItems": 1,
 										"items": {
 											"type": "object",
@@ -793,33 +807,38 @@ export const MCP_TOOLS = {
 												"value": {
 													"type": "string",
 													"description": "The pattern or value to look for in the response. When `type` is 'contains', supports template variable declaration using `{{variable}}` syntax. When `type` is 'regex', can be used to extract variables using regex named groups."
+												}
+											}
+										}
+									},
+									"responseRedactions": {
+										"type": "array",
+										"description": "Portions to select/reveal from the response, applied in order (xPath => jsonPath => regex). Done client-side; only the selected portions (plus the first response line) are sent to the attestor. An independent ordered list — NOT paired 1:1 with `responseMatches`. Mirrors attestor-core `responseRedactions`.",
+										"items": {
+											"type": "object",
+											"additionalProperties": false,
+											"description": "Which portions to select from a response. These are selected in order, xpath => jsonPath => regex * These redactions are done client side and only the selected portions are sent to the attestor. The attestor will only be able to see the selected portions alongside the first line of the HTTP response (i.e. \"HTTP/1.1 200 OK\")",
+											"properties": {
+												"xPath": {
+													"type": "string",
+													"description": "expect an HTML response, and to contain a certain xpath for eg. \"/html/body/div.a1/div.a2/span.a5\""
 												},
-												"extract": {
-													"type": "object",
-													"description": "Which portions to select from a response. These are selected in order, xpath => jsonPath => regex * These redactions are done client side and only the selected portions are sent to the attestor. The attestor will only be able to see the selected portions alongside the first line of the HTTP response (i.e. \"HTTP/1.1 200 OK\")",
-													"properties": {
-														"xPath": {
-															"type": "string",
-															"description": "expect an HTML response, and to contain a certain xpath for eg. \"/html/body/div.a1/div.a2/span.a5\""
-														},
-														"jsonPath": {
-															"type": "string",
-															"description": "expect a JSON response, retrieve the item at this path using dot notation for e.g. 'email.addresses.0'"
-														},
-														"regex": {
-															"type": "string",
-															"description": "select a regex match from the response"
-														},
-														"hash": {
-															"type": "string",
-															"description": "If provided, the value inside will be hashed instead of being redacted. Useful for cases where the data inside is an identifiying piece of information that you don't want to reveal to the attestor, eg. an email address.\nIf the hash function produces more bytes than the original value, the hash will be truncated.\nEg. if hash is enabled, the original value is \"hello\", and hashed is \"a1b2c\", then the attestor will only see \"a1b2c\".\nNote: if a regex with named groups is provided, only the named groups will be hashed.",
-															"enum": [
-																"oprf",
-																"oprf-mpc",
-																"oprf-raw"
-															]
-														}
-													}
+												"jsonPath": {
+													"type": "string",
+													"description": "expect a JSON response, retrieve the item at this path using dot notation for e.g. 'email.addresses.0'"
+												},
+												"regex": {
+													"type": "string",
+													"description": "select a regex match from the response"
+												},
+												"hash": {
+													"type": "string",
+													"description": "If provided, the value inside will be hashed instead of being redacted. Useful for cases where the data inside is an identifiying piece of information that you don't want to reveal to the attestor, eg. an email address.\nIf the hash function produces more bytes than the original value, the hash will be truncated.\nEg. if hash is enabled, the original value is \"hello\", and hashed is \"a1b2c\", then the attestor will only see \"a1b2c\".\nNote: if a regex with named groups is provided, only the named groups will be hashed.",
+													"enum": [
+														"oprf",
+														"oprf-mpc",
+														"oprf-raw"
+													]
 												}
 											}
 										}
@@ -904,9 +923,9 @@ export const MCP_TOOLS = {
 													}
 												}
 											},
-											"matches": {
+											"responseMatches": {
 												"type": "array",
-												"description": "A list of match conditions for the response.",
+												"description": "Conditions the (redacted) response must satisfy for the proof to be valid. Each runs against the union of the portions revealed by `responseRedactions` (or the whole response when there are none). Mirrors attestor-core `responseMatches`.",
 												"minItems": 1,
 												"items": {
 													"type": "object",
@@ -944,33 +963,38 @@ export const MCP_TOOLS = {
 														"value": {
 															"type": "string",
 															"description": "The pattern or value to look for in the response. When `type` is 'contains', supports template variable declaration using `{{variable}}` syntax. When `type` is 'regex', can be used to extract variables using regex named groups."
+														}
+													}
+												}
+											},
+											"responseRedactions": {
+												"type": "array",
+												"description": "Portions to select/reveal from the response, applied in order (xPath => jsonPath => regex). Done client-side; only the selected portions (plus the first response line) are sent to the attestor. An independent ordered list — NOT paired 1:1 with `responseMatches`. Mirrors attestor-core `responseRedactions`.",
+												"items": {
+													"type": "object",
+													"additionalProperties": false,
+													"description": "Which portions to select from a response. These are selected in order, xpath => jsonPath => regex * These redactions are done client side and only the selected portions are sent to the attestor. The attestor will only be able to see the selected portions alongside the first line of the HTTP response (i.e. \"HTTP/1.1 200 OK\")",
+													"properties": {
+														"xPath": {
+															"type": "string",
+															"description": "expect an HTML response, and to contain a certain xpath for eg. \"/html/body/div.a1/div.a2/span.a5\""
+														},
+														"jsonPath": {
+															"type": "string",
+															"description": "expect a JSON response, retrieve the item at this path using dot notation for e.g. 'email.addresses.0'"
 														},
-														"extract": {
-															"type": "object",
-															"description": "Which portions to select from a response. These are selected in order, xpath => jsonPath => regex * These redactions are done client side and only the selected portions are sent to the attestor. The attestor will only be able to see the selected portions alongside the first line of the HTTP response (i.e. \"HTTP/1.1 200 OK\")",
-															"properties": {
-																"xPath": {
-																	"type": "string",
-																	"description": "expect an HTML response, and to contain a certain xpath for eg. \"/html/body/div.a1/div.a2/span.a5\""
-																},
-																"jsonPath": {
-																	"type": "string",
-																	"description": "expect a JSON response, retrieve the item at this path using dot notation for e.g. 'email.addresses.0'"
-																},
-																"regex": {
-																	"type": "string",
-																	"description": "select a regex match from the response"
-																},
-																"hash": {
-																	"type": "string",
-																	"description": "If provided, the value inside will be hashed instead of being redacted. Useful for cases where the data inside is an identifiying piece of information that you don't want to reveal to the attestor, eg. an email address.\nIf the hash function produces more bytes than the original value, the hash will be truncated.\nEg. if hash is enabled, the original value is \"hello\", and hashed is \"a1b2c\", then the attestor will only see \"a1b2c\".\nNote: if a regex with named groups is provided, only the named groups will be hashed.",
-																	"enum": [
-																		"oprf",
-																		"oprf-mpc",
-																		"oprf-raw"
-																	]
-																}
-															}
+														"regex": {
+															"type": "string",
+															"description": "select a regex match from the response"
+														},
+														"hash": {
+															"type": "string",
+															"description": "If provided, the value inside will be hashed instead of being redacted. Useful for cases where the data inside is an identifiying piece of information that you don't want to reveal to the attestor, eg. an email address.\nIf the hash function produces more bytes than the original value, the hash will be truncated.\nEg. if hash is enabled, the original value is \"hello\", and hashed is \"a1b2c\", then the attestor will only see \"a1b2c\".\nNote: if a regex with named groups is provided, only the named groups will be hashed.",
+															"enum": [
+																"oprf",
+																"oprf-mpc",
+																"oprf-raw"
+															]
 														}
 													}
 												}
@@ -1134,30 +1158,45 @@ export const MCP_TOOLS = {
 				"body": {
 					"type": "object",
 					"additionalProperties": false,
-					"description": "Body for `POST /verifications/sessions`. Authenticated by the consumer's `OrgToken`. Carries no callback URLs — they come from the org's callback subscriptions.",
+					"description": "Body for `POST /verifications/sessions`. Authenticated by the consumer's `OrgToken`. Carries no callback URLs — they come from the org's callback subscriptions. The one shared `context` is validated against every provider's `requiredContext`.",
 					"required": [
-						"providerId",
+						"providers",
 						"context",
 						"verificationClientUrl"
 					],
 					"properties": {
-						"providerId": {
-							"type": "string",
-							"format": "uuid"
-						},
-						"version": {
-							"type": "string",
-							"description": "Semver constraint; empty resolves to the latest trunk version.",
-							"maxLength": 64
+						"providers": {
+							"type": "array",
+							"minItems": 1,
+							"description": "Providers to verify, in run order. The Verification Client runs each sequentially in one browser session and submits one combined result; all are required.",
+							"items": {
+								"type": "object",
+								"additionalProperties": false,
+								"description": "A provider (+ optional version) to verify in a session.",
+								"required": [
+									"providerId"
+								],
+								"properties": {
+									"providerId": {
+										"type": "string",
+										"format": "uuid"
+									},
+									"version": {
+										"type": "string",
+										"description": "Semver constraint; empty resolves to the latest trunk version.",
+										"maxLength": 64
+									}
+								}
+							}
 						},
 						"context": {
 							"type": "object",
 							"additionalProperties": true,
-							"description": "Consumer context. Validated against the resolved provider version's `requiredContext` JSON Schema (a 400 is returned on mismatch); extra fields are always allowed. Recipe requests reference these values as `{{context.<key>}}`. Echoed back (plus `reclaimSessionId`) in the result."
+							"description": "Consumer context, shared by all providers. Validated against EACH resolved provider version's `requiredContext` JSON Schema (a 400 is returned on mismatch); extra fields are always allowed. Recipe requests reference these values as `{{context.<key>}}`. Echoed back (plus `reclaimSessionId`) in the result."
 						},
 						"verificationClientUrl": {
 							"type": "string",
-							"description": "Must contain a `{sessionId}` placeholder.",
+							"description": "Must contain a `{sessionId}` placeholder. Must be an http(s) URL.",
 							"maxLength": 2000
 						}
 					}
@@ -1309,8 +1348,8 @@ export const MCP_TOOLS = {
 			"additionalProperties": false
 		}),
 	},
-	"DeleteOrgCredential": {
-		description: "Clear the organization's encryption credential\n\nRemoves the organization's encryption credential. After this, terminal results are delivered as plaintext until a new credential is set. Authenticated by the org's `OrgToken` or a human `BearerAuth` session for an active member of the org.",
+	"DeleteOrgKeypair": {
+		description: "Clear the organization's encryption keypair\n\nRemoves the organization's encryption keypair (the org reverts to keyless ⇒ plaintext delivery, and loses its eth identity address) until a new keypair is set. Authenticated by the org's `OrgToken` or a human `BearerAuth` session for an active member of the org.",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -1440,6 +1479,102 @@ export const MCP_TOOLS = {
 			"additionalProperties": false
 		}),
 	},
+	"DiscoverDataPoints": {
+		description: "List the verifiable data points on a website\n\nThe data points existing providers can prove on a website — the menu to pick from before `GET /discover/resolve`. Optionally filter by `q`.",
+		inputSchema: toZod({
+			"type": "object",
+			"properties": {
+				"params": {
+					"type": "object",
+					"properties": {
+
+					}
+				},
+				"query": {
+					"type": "object",
+					"properties": {
+						"domain": {
+							"type": "string",
+							"format": "hostname",
+							"minLength": 1,
+							"maxLength": 200
+						},
+						"q": {
+							"type": "string",
+							"maxLength": 200
+						}
+					},
+					"required": [
+						"domain"
+					],
+					"additionalProperties": false
+				},
+				"body": {
+					"type": "object"
+				}
+			},
+			"required": [
+				"params",
+				"query"
+			],
+			"additionalProperties": false
+		}),
+	},
+	"DiscoverResolve": {
+		description: "Resolve a website + data points to verification providers\n\nProvider resolution: given a website and the data points the user wants their users to prove, return the smallest set of existing providers whose data points COVER the selection (greedy combine), the `requiredContext` inputs the consumer must supply, and any `uncovered` points no provider exposes yet (`needsCreation` is true then — author a provider with the agent tools). When the chosen providers can be fused into one (same start page, no clashing page scripts) `merge.mergeable` is true.\n\nAgent flow: pick a website (`GET /discover/data-points` lists what's verifiable there), confirm the data points with the user, call this to get the `providers` + `requiredContext`, collect those context values from the user, then `POST /verifications/sessions` with `providers` (pass every id) and `context` to mint a verification.",
+		inputSchema: toZod({
+			"type": "object",
+			"properties": {
+				"params": {
+					"type": "object",
+					"properties": {
+
+					}
+				},
+				"query": {
+					"type": "object",
+					"properties": {
+						"domain": {
+							"type": "string",
+							"format": "hostname",
+							"minLength": 1,
+							"maxLength": 200
+						},
+						"dataPoints": {
+							"type": "array",
+							"minItems": 1,
+							"maxItems": 200,
+							"items": {
+								"type": "string",
+								"minLength": 1,
+								"maxLength": 200
+							}
+						},
+						"mode": {
+							"type": "string",
+							"enum": [
+								"combine",
+								"ai"
+							]
+						}
+					},
+					"required": [
+						"domain",
+						"dataPoints"
+					],
+					"additionalProperties": false
+				},
+				"body": {
+					"type": "object"
+				}
+			},
+			"required": [
+				"params",
+				"query"
+			],
+			"additionalProperties": false
+		}),
+	},
 	"GetAttachSession": {
 		description: "Poll a pairing session\n\nAnonymous poll endpoint used by the CLI / MCP while it waits for the human to complete the dashboard step. Once `status` is `LINKED`, the response includes a `token` (2-day bearer token) the CLI / MCP can use for authenticated API calls. Expired or unknown codes return `404`.",
 		inputSchema: toZod({
@@ -1527,7 +1662,17 @@ export const MCP_TOOLS = {
 				"query": {
 					"type": "object",
 					"properties": {
-
+						"tab": {
+							"type": "string",
+							"enum": [
+								"connect",
+								"providers",
+								"members",
+								"themes",
+								"sessions",
+								"billing"
+							]
+						}
 					}
 				},
 				"body": {
@@ -1576,8 +1721,8 @@ export const MCP_TOOLS = {
 			"additionalProperties": false
 		}),
 	},
-	"GetOrgCredential": {
-		description: "Get the organization's encryption credential\n\nReturns the organization's single X25519 encryption credential — the public JWK the Builder uses to JWE-encrypt delivered results — or `404` when none is set (delivery is plaintext in that case). Authenticated by the org's `OrgToken` or a human `BearerAuth` session for an active member of the org.",
+	"GetOrgKeypair": {
+		description: "Get the organization's encryption keypair\n\nReturns the organization's single Ethereum (secp256k1) encryption keypair — its public JWK, derived eth address, and `canEncryptResult` flag — or `404` when none is set (the org is keyless ⇒ plaintext delivery). Authenticated by the org's `OrgToken` or a human `BearerAuth` session for an active member of the org.",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -2190,7 +2335,6 @@ export const MCP_TOOLS = {
 					"properties": {
 						"q": {
 							"type": "string",
-							"minLength": 1,
 							"maxLength": 200
 						},
 						"tag": {
@@ -2353,8 +2497,8 @@ export const MCP_TOOLS = {
 			"additionalProperties": false
 		}),
 	},
-	"SetOrgCredential": {
-		description: "Set (or replace) the organization's encryption credential\n\nUpserts the organization's single X25519 encryption credential. The body carries the org's **encryption public JWK** (`{kty:'OKP', crv:'X25519', x}`); the matching private key never leaves the consumer. Replacing overwrites the single row. Once set, terminal results are delivered as a compact JWE encrypted to this key; clear it to revert to plaintext delivery. Authenticated by the org's `OrgToken` or a human `BearerAuth` session for an active member of the org.",
+	"SetOrgKeypair": {
+		description: "Set (or rotate) the organization's encryption keypair\n\nUpserts the organization's single Ethereum (secp256k1) encryption keypair. The body carries the org's **eth public key** — as an uncompressed hex string (`0x04`+128 hex) or a secp256k1 public JWK (`{kty:'EC', crv:'secp256k1', x, y}`) — and `canEncryptResult`. The matching private key never leaves the consumer. Setting overwrites the single row (and creates it for a keyless org). When `canEncryptResult` is true, terminal results are delivered as an ECIES ciphertext encrypted to this key; otherwise plaintext. Authenticated by the org's `OrgToken` or a human `BearerAuth` session for an active member of the org.",
 		inputSchema: toZod({
 			"type": "object",
 			"properties": {
@@ -2378,49 +2522,88 @@ export const MCP_TOOLS = {
 					}
 				},
 				"body": {
-					"type": "object",
-					"additionalProperties": false,
-					"description": "Body for `PUT /orgs/{orgId}/credential`.",
-					"required": [
-						"publicKeyJwk"
-					],
-					"properties": {
-						"publicKeyJwk": {
+					"oneOf": [
+						{
 							"type": "object",
 							"additionalProperties": false,
-							"description": "An X25519 public key in JWK form (RFC 8037 OKP), used to JWE-encrypt delivered verification results. The matching private key never leaves the consumer.",
+							"description": "Body for `PUT /orgs/{orgId}/keypair`. Carries the org's eth public key as an uncompressed hex string (`0x04` + 128 hex) — the eth-native form wallets/ethers emit. The matching private key never leaves the consumer.",
 							"required": [
-								"kty",
-								"crv",
-								"x"
+								"publicKey"
 							],
 							"properties": {
-								"kty": {
+								"publicKey": {
 									"type": "string",
-									"enum": [
-										"OKP"
-									]
+									"description": "Uncompressed secp256k1 public key, `0x04` + 128 hex.",
+									"pattern": "^0x04[0-9a-fA-F]{128}$"
 								},
-								"crv": {
-									"type": "string",
-									"enum": [
-										"X25519"
-									]
+								"canEncryptResult": {
+									"type": "boolean",
+									"default": false
 								},
-								"x": {
+								"label": {
 									"type": "string",
-									"description": "base64url-encoded public key bytes.",
 									"minLength": 1,
-									"maxLength": 128
+									"maxLength": 100
 								}
 							}
 						},
-						"label": {
-							"type": "string",
-							"minLength": 1,
-							"maxLength": 100
+						{
+							"type": "object",
+							"additionalProperties": false,
+							"description": "Body for `PUT /orgs/{orgId}/keypair`. Carries the org's eth public key as a secp256k1 public JWK.",
+							"required": [
+								"publicKeyJwk"
+							],
+							"properties": {
+								"publicKeyJwk": {
+									"type": "object",
+									"additionalProperties": false,
+									"description": "A secp256k1 (Ethereum) public key in JWK form (`{kty:'EC', crv:'secp256k1', x, y}`), used to ECIES-encrypt delivered verification results and to identify the org. The matching private key never leaves the consumer. Same shape published by the signing JWKS.",
+									"required": [
+										"kty",
+										"crv",
+										"x",
+										"y"
+									],
+									"properties": {
+										"kty": {
+											"type": "string",
+											"enum": [
+												"EC"
+											]
+										},
+										"crv": {
+											"type": "string",
+											"enum": [
+												"secp256k1"
+											]
+										},
+										"x": {
+											"type": "string",
+											"description": "base64url-encoded X coordinate (32 bytes).",
+											"minLength": 1,
+											"maxLength": 64
+										},
+										"y": {
+											"type": "string",
+											"description": "base64url-encoded Y coordinate (32 bytes).",
+											"minLength": 1,
+											"maxLength": 64
+										}
+									}
+								},
+								"canEncryptResult": {
+									"type": "boolean",
+									"default": false
+								},
+								"label": {
+									"type": "string",
+									"minLength": 1,
+									"maxLength": 100
+								}
+							}
 						}
-					}
+					]
 				}
 			},
 			"required": [
@@ -2528,44 +2711,6 @@ export const MCP_TOOLS = {
 			"additionalProperties": false
 		}),
 	},
-	"UpdateMe": {
-		description: "Update the authenticated user's profile",
-		inputSchema: toZod({
-			"type": "object",
-			"properties": {
-				"params": {
-					"type": "object",
-					"properties": {
-
-					}
-				},
-				"query": {
-					"type": "object",
-					"properties": {
-
-					}
-				},
-				"body": {
-					"type": "object",
-					"additionalProperties": false,
-					"description": "Caller-editable fields on the authenticated user.",
-					"properties": {
-						"name": {
-							"type": "string",
-							"minLength": 1,
-							"maxLength": 200
-						}
-					}
-				}
-			},
-			"required": [
-				"params",
-				"query",
-				"body"
-			],
-			"additionalProperties": false
-		}),
-	},
 	"UpdateOrg": {
 		description: "Update an organization\n\nOwner only.",
 		inputSchema: toZod({
@@ -2935,9 +3080,9 @@ export const MCP_TOOLS = {
 											}
 										}
 									},
-									"matches": {
+									"responseMatches": {
 										"type": "array",
-										"description": "A list of match conditions for the response.",
+										"description": "Conditions the (redacted) response must satisfy for the proof to be valid. Each runs against the union of the portions revealed by `responseRedactions` (or the whole response when there are none). Mirrors attestor-core `responseMatches`.",
 										"minItems": 1,
 										"items": {
 											"type": "object",
@@ -2975,33 +3120,38 @@ export const MCP_TOOLS = {
 												"value": {
 													"type": "string",
 													"description": "The pattern or value to look for in the response. When `type` is 'contains', supports template variable declaration using `{{variable}}` syntax. When `type` is 'regex', can be used to extract variables using regex named groups."
+												}
+											}
+										}
+									},
+									"responseRedactions": {
+										"type": "array",
+										"description": "Portions to select/reveal from the response, applied in order (xPath => jsonPath => regex). Done client-side; only the selected portions (plus the first response line) are sent to the attestor. An independent ordered list — NOT paired 1:1 with `responseMatches`. Mirrors attestor-core `responseRedactions`.",
+										"items": {
+											"type": "object",
+											"additionalProperties": false,
+											"description": "Which portions to select from a response. These are selected in order, xpath => jsonPath => regex * These redactions are done client side and only the selected portions are sent to the attestor. The attestor will only be able to see the selected portions alongside the first line of the HTTP response (i.e. \"HTTP/1.1 200 OK\")",
+											"properties": {
+												"xPath": {
+													"type": "string",
+													"description": "expect an HTML response, and to contain a certain xpath for eg. \"/html/body/div.a1/div.a2/span.a5\""
 												},
-												"extract": {
-													"type": "object",
-													"description": "Which portions to select from a response. These are selected in order, xpath => jsonPath => regex * These redactions are done client side and only the selected portions are sent to the attestor. The attestor will only be able to see the selected portions alongside the first line of the HTTP response (i.e. \"HTTP/1.1 200 OK\")",
-													"properties": {
-														"xPath": {
-															"type": "string",
-															"description": "expect an HTML response, and to contain a certain xpath for eg. \"/html/body/div.a1/div.a2/span.a5\""
-														},
-														"jsonPath": {
-															"type": "string",
-															"description": "expect a JSON response, retrieve the item at this path using dot notation for e.g. 'email.addresses.0'"
-														},
-														"regex": {
-															"type": "string",
-															"description": "select a regex match from the response"
-														},
-														"hash": {
-															"type": "string",
-															"description": "If provided, the value inside will be hashed instead of being redacted. Useful for cases where the data inside is an identifiying piece of information that you don't want to reveal to the attestor, eg. an email address.\nIf the hash function produces more bytes than the original value, the hash will be truncated.\nEg. if hash is enabled, the original value is \"hello\", and hashed is \"a1b2c\", then the attestor will only see \"a1b2c\".\nNote: if a regex with named groups is provided, only the named groups will be hashed.",
-															"enum": [
-																"oprf",
-																"oprf-mpc",
-																"oprf-raw"
-															]
-														}
-													}
+												"jsonPath": {
+													"type": "string",
+													"description": "expect a JSON response, retrieve the item at this path using dot notation for e.g. 'email.addresses.0'"
+												},
+												"regex": {
+													"type": "string",
+													"description": "select a regex match from the response"
+												},
+												"hash": {
+													"type": "string",
+													"description": "If provided, the value inside will be hashed instead of being redacted. Useful for cases where the data inside is an identifiying piece of information that you don't want to reveal to the attestor, eg. an email address.\nIf the hash function produces more bytes than the original value, the hash will be truncated.\nEg. if hash is enabled, the original value is \"hello\", and hashed is \"a1b2c\", then the attestor will only see \"a1b2c\".\nNote: if a regex with named groups is provided, only the named groups will be hashed.",
+													"enum": [
+														"oprf",
+														"oprf-mpc",
+														"oprf-raw"
+													]
 												}
 											}
 										}
@@ -3083,9 +3233,9 @@ export const MCP_TOOLS = {
 													}
 												}
 											},
-											"matches": {
+											"responseMatches": {
 												"type": "array",
-												"description": "A list of match conditions for the response.",
+												"description": "Conditions the (redacted) response must satisfy for the proof to be valid. Each runs against the union of the portions revealed by `responseRedactions` (or the whole response when there are none). Mirrors attestor-core `responseMatches`.",
 												"minItems": 1,
 												"items": {
 													"type": "object",
@@ -3123,33 +3273,38 @@ export const MCP_TOOLS = {
 														"value": {
 															"type": "string",
 															"description": "The pattern or value to look for in the response. When `type` is 'contains', supports template variable declaration using `{{variable}}` syntax. When `type` is 'regex', can be used to extract variables using regex named groups."
+														}
+													}
+												}
+											},
+											"responseRedactions": {
+												"type": "array",
+												"description": "Portions to select/reveal from the response, applied in order (xPath => jsonPath => regex). Done client-side; only the selected portions (plus the first response line) are sent to the attestor. An independent ordered list — NOT paired 1:1 with `responseMatches`. Mirrors attestor-core `responseRedactions`.",
+												"items": {
+													"type": "object",
+													"additionalProperties": false,
+													"description": "Which portions to select from a response. These are selected in order, xpath => jsonPath => regex * These redactions are done client side and only the selected portions are sent to the attestor. The attestor will only be able to see the selected portions alongside the first line of the HTTP response (i.e. \"HTTP/1.1 200 OK\")",
+													"properties": {
+														"xPath": {
+															"type": "string",
+															"description": "expect an HTML response, and to contain a certain xpath for eg. \"/html/body/div.a1/div.a2/span.a5\""
+														},
+														"jsonPath": {
+															"type": "string",
+															"description": "expect a JSON response, retrieve the item at this path using dot notation for e.g. 'email.addresses.0'"
+														},
+														"regex": {
+															"type": "string",
+															"description": "select a regex match from the response"
 														},
-														"extract": {
-															"type": "object",
-															"description": "Which portions to select from a response. These are selected in order, xpath => jsonPath => regex * These redactions are done client side and only the selected portions are sent to the attestor. The attestor will only be able to see the selected portions alongside the first line of the HTTP response (i.e. \"HTTP/1.1 200 OK\")",
-															"properties": {
-																"xPath": {
-																	"type": "string",
-																	"description": "expect an HTML response, and to contain a certain xpath for eg. \"/html/body/div.a1/div.a2/span.a5\""
-																},
-																"jsonPath": {
-																	"type": "string",
-																	"description": "expect a JSON response, retrieve the item at this path using dot notation for e.g. 'email.addresses.0'"
-																},
-																"regex": {
-																	"type": "string",
-																	"description": "select a regex match from the response"
-																},
-																"hash": {
-																	"type": "string",
-																	"description": "If provided, the value inside will be hashed instead of being redacted. Useful for cases where the data inside is an identifiying piece of information that you don't want to reveal to the attestor, eg. an email address.\nIf the hash function produces more bytes than the original value, the hash will be truncated.\nEg. if hash is enabled, the original value is \"hello\", and hashed is \"a1b2c\", then the attestor will only see \"a1b2c\".\nNote: if a regex with named groups is provided, only the named groups will be hashed.",
-																	"enum": [
-																		"oprf",
-																		"oprf-mpc",
-																		"oprf-raw"
-																	]
-																}
-															}
+														"hash": {
+															"type": "string",
+															"description": "If provided, the value inside will be hashed instead of being redacted. Useful for cases where the data inside is an identifiying piece of information that you don't want to reveal to the attestor, eg. an email address.\nIf the hash function produces more bytes than the original value, the hash will be truncated.\nEg. if hash is enabled, the original value is \"hello\", and hashed is \"a1b2c\", then the attestor will only see \"a1b2c\".\nNote: if a regex with named groups is provided, only the named groups will be hashed.",
+															"enum": [
+																"oprf",
+																"oprf-mpc",
+																"oprf-raw"
+															]
 														}
 													}
 												}