Validate OpenRTB bid requests and responses against IAB specs. ARTF, Rust core.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
AdCP protocol discovery. Returns the AdCP releases this agent speaks and the bid-stream conformance metrics it computes. Call this first when wiring rtblint into an agentic buying pipeline: it declares the experimental measurement protocol and the metric ids (openrtb_error_count, openrtb_warning_count, openrtb_conformance_rate) that validate_bid_request and validate_bid_response produce. Part of the Ad Context Protocol (AdCP 3.1) specification.
Caller extension object. Accepted and ignored; declared so envelope fields do not trip strict request-wrapper validation.
Caller-supplied context object. Echoed back unchanged in the response.
Filter which per-protocol capability blocks are returned. Does not narrow supported_protocols, which declares what the agent implements.
Release-precision AdCP version the caller pins (for example "3.1"). When the pin is not in supported_versions the call returns a VERSION_UNSUPPORTED error naming the releases that would work. When omitted, the highest supported release is served.
AdCP 3.1 carries an idempotency key on every task request, reads included. This agent has no mutating surface and no replay store, so the key is accepted and ignored rather than rejected as an unknown field.
Deprecated in favour of adcp_version. AdCP major version the caller's payloads conform to. When omitted, assumes the highest supported major.
AdCP protocol discovery. Returns the AdCP releases this agent speaks and the bid-stream conformance metrics it computes. Call this first when wiring rtblint into an agentic buying pipeline: it declares the experimental measurement protocol and the metric ids (openrtb_error_count, openrtb_warning_count, openrtb_conformance_rate) that validate_bid_request and validate_bid_response produce. Part of the Ad Context Protocol (AdCP 3.1) specification.
| Argument | Type | Description |
|---|---|---|
| ext | object | Caller extension object. Accepted and ignored; declared so envelope fields do not trip strict request-wrapper validation. |
| context | object | Caller-supplied context object. Echoed back unchanged in the response. |
| protocols | array | Filter which per-protocol capability blocks are returned. Does not narrow supported_protocols, which declares what the agent implements. |
| adcp_version | string | Release-precision AdCP version the caller pins (for example "3.1"). When the pin is not in supported_versions the call returns a VERSION_UNSUPPORTED error naming the releases that would work. When omitted, the highest supported release is served. |
| idempotency_key | string | AdCP 3.1 carries an idempotency key on every task request, reads included. This agent has no mutating surface and no replay store, so the key is accepted and ignored rather than rejected as an unknown field. |
| adcp_major_version | integer | Deprecated in favour of adcp_version. AdCP major version the caller's payloads conform to. When omitted, assumes the highest supported major. |
{
"type": "object",
"title": "GetAdcpCapabilitiesInput",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"ext": {
"type": "object",
"description": "Caller extension object. Accepted and ignored; declared so envelope fields do not trip strict request-wrapper validation."
},
"context": {
"type": "object",
"description": "Caller-supplied context object. Echoed back unchanged in the response."
},
"protocols": {
"type": "array",
"items": {
"type": "string"
},
"description": "Filter which per-protocol capability blocks are returned. Does not narrow supported_protocols, which declares what the agent implements."
},
"adcp_version": {
"type": "string",
"description": "Release-precision AdCP version the caller pins (for example \"3.1\"). When the pin is not in supported_versions the call returns a VERSION_UNSUPPORTED error naming the releases that would work. When omitted, the highest supported release is served."
},
"idempotency_key": {
"type": "string",
"description": "AdCP 3.1 carries an idempotency key on every task request, reads included. This agent has no mutating surface and no replay store, so the key is accepted and ignored rather than rejected as an unknown field."
},
"adcp_major_version": {
"type": "integer",
"description": "Deprecated in favour of adcp_version. AdCP major version the caller's payloads conform to. When omitted, assumes the highest supported major."
}
}
}List every OpenRTB version id this build can validate against, from 2.0 through the monthly 2.6 snapshots. Call this before pinning version on a validate_* tool.
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}Validate an ARTF (IAB Tech Lab Agentic Real Time Framework) RTBRequest envelope: required members, lifecycle and payload coherence, tmax plausibility, originator and applicable_intents enums, plus full OpenRTB validation of the bid request and bid response it carries. The carried payloads are protobuf JSON, so they are validated in that dialect.
| Argument | Type | Description |
|---|---|---|
| payload* | string | The ARTF RTBRequest envelope as a raw JSON string. |
| version | string | OpenRTB version id to validate against (default 2.6-202606). One of: 2.0, 2.1, 2.2, 2.3, 2.3.1, 2.4, 2.5, 2.6-202204, 2.6-202210, 2.6-202211, 2.6-202303, 2.6-202309, 2.6-202402, 2.6-202409, 2.6-202501, 2.6-202505, 2.6-202606, 3.0 |
| sample_kind | string | Label test-generated payloads as synthetic in validation telemetry. |
{
"type": "object",
"required": [
"payload"
],
"properties": {
"payload": {
"type": "string",
"description": "The ARTF RTBRequest envelope as a raw JSON string."
},
"version": {
"type": "string",
"description": "OpenRTB version id to validate against (default 2.6-202606). One of: 2.0, 2.1, 2.2, 2.3, 2.3.1, 2.4, 2.5, 2.6-202204, 2.6-202210, 2.6-202211, 2.6-202303, 2.6-202309, 2.6-202402, 2.6-202409, 2.6-202501, 2.6-202505, 2.6-202606, 3.0"
},
"sample_kind": {
"enum": [
"submitted",
"synthetic"
],
"type": "string",
"description": "Label test-generated payloads as synthetic in validation telemetry."
}
}
}Validate an ARTF RTBResponse mutation set against the RTBRequest it answers: envelope id echo, declared intent against applicable_intents, operation and payload coherence, and whether each semantic path (/imp/{id}, /imp/{id}/pmp/deals/{id}, /user/data/segment, /seatbid/{seat}/bid/{id}) resolves to something the auction actually carries. With apply=true the mutations are written into the payloads and revalidated, reporting the OpenRTB findings the mutations introduced. Call this before proposing mutations to an orchestrator.
| Argument | Type | Description |
|---|---|---|
| apply | boolean | Apply the mutations and revalidate the result (default false). Returns the mutated payloads and the findings the mutations introduced, with pre-existing findings filtered out. |
| payload* | string | The ARTF RTBResponse as a raw JSON string. |
| version | string | OpenRTB version id to validate against (default 2.6-202606). One of: 2.0, 2.1, 2.2, 2.3, 2.3.1, 2.4, 2.5, 2.6-202204, 2.6-202210, 2.6-202211, 2.6-202303, 2.6-202309, 2.6-202402, 2.6-202409, 2.6-202501, 2.6-202505, 2.6-202606, 3.0 |
| rtb_request* | string | The ARTF RTBRequest envelope this response answers, as a raw JSON string. Required: a mutation is only meaningful relative to the auction it targets. |
| sample_kind | string | Label test-generated payloads as synthetic in validation telemetry. |
Validate an OpenRTB 2.x bid request JSON payload against a tracked spec version. Returns structured issues with rule ids, severities, and JSON paths.
| Argument | Type | Description |
|---|---|---|
| dialect | string | JSON dialect the payload is written in. spec-json (default) types flag fields such as imp.secure, regs.coppa and pmp.private_auction as integers, the way the OpenRTB specification does. proto-json follows the IAB OpenRTB protobuf schema, which declares 28 of those fields bool, so true/false is correct there and an integer is the error. Use proto-json for anything that came off a gRPC bidstream integration. |
| payload* | string | The OpenRTB bid request as a raw JSON string. |
| profile | string | Published vendor constraints on top of the selected spec. Choose the matching traffic direction. spec is the default. xandr targets Microsoft Monetize bidder traffic; magnite targets DV+ xAPI. Buyer, supplier and SDK profiles have distinct contracts. Optional extension fields remain optional unless the source explicitly requires them. A direction without a verified contract applies canonical checks and returns a scope warning. |
| version | string | OpenRTB version id to validate against (default 2.6-202606). One of: 2.0, 2.1, 2.2, 2.3, 2.3.1, 2.4, 2.5, 2.6-202204, 2.6-202210, 2.6-202211, 2.6-202303, 2.6-202309, 2.6-202402, 2.6-202409, 2.6-202501, 2.6-202505, 2.6-202606, 3.0 |
| sample_kind | string |
Validate an OpenRTB 2.x bid response JSON payload against a tracked spec version. Optionally cross-validate it against the originating bid request (impid, mtype, adm markup, dealid, seat, and currency coherence). Returns structured issues with rule ids, severities, and JSON paths.
| Argument | Type | Description |
|---|---|---|
| dialect | string | JSON dialect the payload is written in. spec-json (default) types flag fields such as imp.secure, regs.coppa and pmp.private_auction as integers, the way the OpenRTB specification does. proto-json follows the IAB OpenRTB protobuf schema, which declares 28 of those fields bool, so true/false is correct there and an integer is the error. Use proto-json for anything that came off a gRPC bidstream integration. |
| payload* | string | The OpenRTB bid response as a raw JSON string. |
| profile | string | Published vendor constraints on top of the selected spec. Choose the matching traffic direction. spec is the default. xandr targets Microsoft Monetize bidder traffic; magnite targets DV+ xAPI. Buyer, supplier and SDK profiles have distinct contracts. Optional extension fields remain optional unless the source explicitly requires them. A direction without a verified contract applies canonical checks and returns a scope warning. |
| version | string | OpenRTB version id to validate against (default 2.6-202606). One of: 2.0, 2.1, 2.2, 2.3, 2.3.1, 2.4, 2.5, 2.6-202204, 2.6-202210, 2.6-202211, 2.6-202303, 2.6-202309, 2.6-202402, 2.6-202409, 2.6-202501, 2.6-202505, 2.6-202606, 3.0 |
{
"type": "object",
"required": [
"payload",
"rtb_request"
],
"properties": {
"apply": {
"type": "boolean",
"description": "Apply the mutations and revalidate the result (default false). Returns the mutated payloads and the findings the mutations introduced, with pre-existing findings filtered out."
},
"payload": {
"type": "string",
"description": "The ARTF RTBResponse as a raw JSON string."
},
"version": {
"type": "string",
"description": "OpenRTB version id to validate against (default 2.6-202606). One of: 2.0, 2.1, 2.2, 2.3, 2.3.1, 2.4, 2.5, 2.6-202204, 2.6-202210, 2.6-202211, 2.6-202303, 2.6-202309, 2.6-202402, 2.6-202409, 2.6-202501, 2.6-202505, 2.6-202606, 3.0"
},
"rtb_request": {
"type": "string",
"description": "The ARTF RTBRequest envelope this response answers, as a raw JSON string. Required: a mutation is only meaningful relative to the auction it targets."
},
"sample_kind": {
"enum": [
"submitted",
"synthetic"
],
"type": "string",
"description": "Label test-generated payloads as synthetic in validation telemetry."
}
}
}| Label test-generated payloads as synthetic in validation telemetry. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"payload"
],
"properties": {
"dialect": {
"enum": [
"spec-json",
"proto-json"
],
"type": "string",
"description": "JSON dialect the payload is written in. spec-json (default) types flag fields such as imp.secure, regs.coppa and pmp.private_auction as integers, the way the OpenRTB specification does. proto-json follows the IAB OpenRTB protobuf schema, which declares 28 of those fields bool, so true/false is correct there and an integer is the error. Use proto-json for anything that came off a gRPC bidstream integration."
},
"payload": {
"type": "string",
"description": "The OpenRTB bid request as a raw JSON string."
},
"profile": {
"enum": [
"spec",
"google-ab",
"prebid-server",
"xandr",
"magnite",
"dv360",
"index-exchange",
"index-exchange-seller",
"unity",
"vungle",
"bidswitch",
"bidswitch-supplier",
"inmobi",
"inmobi-supplier",
"mobilefuse",
"mobilefuse-sdk",
"applovin-alx",
"commerce-grid",
"digital-turbine",
"sovrn",
"equativ",
"equativ-supplier",
"triplelift-supplier",
"adform-handler",
"yandex-sdk-bidding",
"pubmatic-openwrap",
"pubmatic-openwrap-ctv"
],
"type": "string",
"description": "Published vendor constraints on top of the selected spec. Choose the matching traffic direction. spec is the default. xandr targets Microsoft Monetize bidder traffic; magnite targets DV+ xAPI. Buyer, supplier and SDK profiles have distinct contracts. Optional extension fields remain optional unless the source explicitly requires them. A direction without a verified contract applies canonical checks and returns a scope warning."
},
"version": {
"type": "string",
"description": "OpenRTB version id to validate against (default 2.6-202606). One of: 2.0, 2.1, 2.2, 2.3, 2.3.1, 2.4, 2.5, 2.6-202204, 2.6-202210, 2.6-202211, 2.6-202303, 2.6-202309, 2.6-202402, 2.6-202409, 2.6-202501, 2.6-202505, 2.6-202606, 3.0"
},
"sample_kind": {
"enum": [
"submitted",
"synthetic"
],
"type": "string",
"description": "Label test-generated payloads as synthetic in validation telemetry."
}
}
}| bid_request |
| string |
| Optional: the originating OpenRTB bid request as a raw JSON string. When supplied, every bid is also cross-checked against the Imp it references. |
| sample_kind | string | Label test-generated payloads as synthetic in validation telemetry. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"payload"
],
"properties": {
"dialect": {
"enum": [
"spec-json",
"proto-json"
],
"type": "string",
"description": "JSON dialect the payload is written in. spec-json (default) types flag fields such as imp.secure, regs.coppa and pmp.private_auction as integers, the way the OpenRTB specification does. proto-json follows the IAB OpenRTB protobuf schema, which declares 28 of those fields bool, so true/false is correct there and an integer is the error. Use proto-json for anything that came off a gRPC bidstream integration."
},
"payload": {
"type": "string",
"description": "The OpenRTB bid response as a raw JSON string."
},
"profile": {
"enum": [
"spec",
"google-ab",
"prebid-server",
"xandr",
"magnite",
"dv360",
"index-exchange",
"index-exchange-seller",
"unity",
"vungle",
"bidswitch",
"bidswitch-supplier",
"inmobi",
"inmobi-supplier",
"mobilefuse",
"mobilefuse-sdk",
"applovin-alx",
"commerce-grid",
"digital-turbine",
"sovrn",
"equativ",
"equativ-supplier",
"triplelift-supplier",
"adform-handler",
"yandex-sdk-bidding",
"pubmatic-openwrap",
"pubmatic-openwrap-ctv"
],
"type": "string",
"description": "Published vendor constraints on top of the selected spec. Choose the matching traffic direction. spec is the default. xandr targets Microsoft Monetize bidder traffic; magnite targets DV+ xAPI. Buyer, supplier and SDK profiles have distinct contracts. Optional extension fields remain optional unless the source explicitly requires them. A direction without a verified contract applies canonical checks and returns a scope warning."
},
"version": {
"type": "string",
"description": "OpenRTB version id to validate against (default 2.6-202606). One of: 2.0, 2.1, 2.2, 2.3, 2.3.1, 2.4, 2.5, 2.6-202204, 2.6-202210, 2.6-202211, 2.6-202303, 2.6-202309, 2.6-202402, 2.6-202409, 2.6-202501, 2.6-202505, 2.6-202606, 3.0"
},
"bid_request": {
"type": "string",
"description": "Optional: the originating OpenRTB bid request as a raw JSON string. When supplied, every bid is also cross-checked against the Imp it references."
},
"sample_kind": {
"enum": [
"submitted",
"synthetic"
],
"type": "string",
"description": "Label test-generated payloads as synthetic in validation telemetry."
}
}
}