Check an API request
check_api_requestCheck an HTTP request for a CDP before you send it: is it a call the CDP's own developer docs document for one of five everyday jobs (send an event, create or update a profile, send a batch, look up a profile, delete a person), on a documented host, with the credential in a documented place and every required header, query parameter and body field? Uses the answer keys of CdpHub's agent readiness test, written by hand from each vendor's reference pages, for the 29 CDPs the test scored. It checks the request's form, not your data, and sends nothing to the vendor. Give the request as an object (method, url, headers, query, body) or as a curl command. Leave the job out to find the job it matches.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"cdp": "<cdp>"
},
"name": "check_api_request"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cdp | Yes | The CDP, by name or CdpHub slug, for example "Braze", "Segment" or "treasure-ai". | |
| job | No | The job the request is for. Leave it out to find the job it matches. | |
| curl | No | The request as a curl command, instead of request. | |
| request | No | The request: method, full url, and headers, query and body as objects. Placeholders in angle brackets are fine. |