Phone APIPOST /agentic-services/api/phone · x402 API by brandontan.app
Telephony API with 8 actions: AI calls, voicemail, SMS, phone number lookup, CNAM, fax, AMD, and voice OTP verification. Variable pricing via x402 on Base.
What does this x402 API do?
Phone API. This is an x402-gated POST API resource from brandontan.app. TOLL·402 did not invoke this route automatically because doing so was not considered safe. No normalized USD price is recorded; the listing names an unspecified network. No settled paid call has been verified.
- Published price
- No normalized USD price is recorded
- Networks
- Not recorded
- Latest evidence
- TOLL·402 did not invoke this route automatically because doing so was not considered safe
- Resource ID
- 6a1d068e93413804f484ca08
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://brandontan.app/agentic-services/api/phone", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"replace": "with provider-approved input"
}),
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.Review the provider input schema before running this non-read-only method. No payment code is included.
- Observed in 402-index
Discovered through self-registered.
- Registry record checked
Registry health: down.
- Exact route checked
not safely testable · potentially-mutating-method:POST
- Origin unavailable
UNSAFE_URL_EAI_AGAIN: https://brandontan.app/
What evidence supports this listing?
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call. Read the discovery and verification methodology →
Which networks and payment options does it accept?
The normalized listing price is No normalized USD price is recorded. Raw protocol requirements remain visible below for implementation and audit use.