Give your agent the warranty wording

A buyer asks whether a used appliance still has warranty coverage. The listing says “two-year warranty.” That leaves the ownership question unanswered.

warranty-parse extracts coverage terms from text you supply. It returns covered defects and exclusions, plus duration in months, claim instructions, and transfer status. A shopping agent can compare those fields across products. A support assistant can use the claim instructions to help a customer prepare a request.

The endpoint costs 0.015 USDC per call, paid through x402 on Base mainnet. Its input is warranty text copied from a manual or manufacturer page. Send the wording itself.

From a paragraph to fields

Call POST https://x402.agentutility.ai/warranty-parse through your x402-capable client with this JSON body: 

{
  "warranty_text": "This warranty covers defects in materials and workmanship for two years from purchase. It excludes water damage and normal wear. To claim, email [email protected] with your receipt and product serial number. Coverage cannot transfer to another owner."
}

This is fictional sample wording. The text field is an accepted alias for warranty_text; use the primary field in new integrations.

The coverage portion of an illustrative response looks like this: 

{
  "coverage": [
    "defects in materials",
    "defects in workmanship"
  ],
  "duration_months": 24,
  "exclusions": [
    "water damage",
    "normal wear"
  ],
  "claim_process": "Email [email protected] with your receipt and product serial number.",
  "transferable": false
}

coverage and exclusions are arrays of strings. An agent can display each extracted item beside the product without asking the buyer to reread the paragraph.

duration_months is numeric when a duration is extracted. Here, two years becomes 24. Keep the original wording alongside that number: the purchase date starts the period in this example, and the response doesn't provide a separate field for that starting condition.

claim_process is a string. It contains the extracted instructions, so your application must turn that text into a checklist if the customer needs one.

And transferable is a boolean when the text states an answer. The sample explicitly prevents transfer, so the result is false.

Silence has a return value

What happens if the warranty says nothing about resale?

transferable should be null. Preserve that distinction in your application. Converting it to false would tell a used-product buyer that transfer is prohibited, even though the supplied text never answers the question.

For this shorter input: 

{
  "warranty_text": "This warranty covers defects in materials."
}

The intended coverage fields are: 

{
  "coverage": ["defects in materials"],
  "duration_months": null,
  "exclusions": [],
  "claim_process": null,
  "transferable": null
}

Unstated scalar fields use null. List fields use empty arrays.

An empty exclusions array means the extraction contains no stated exclusions. It doesn't establish that every kind of damage is covered. Label that state “No exclusions stated in supplied text” so the buyer knows what the result supports.

But missing terms also give your agent a useful next action. If a secondhand purchase depends on transfer rights, ask for the full warranty wording or direct the buyer to the seller for confirmation.

Check the text before acting

The input needs at least 20 characters after trimming. Text longer than 20,000 characters is cut to its first 20,000 characters. The response includes input_chars, which counts the trimmed input before that cutoff, and truncated, which reports whether the cutoff happened.

Check truncated before presenting the record as a reading of the whole document. A transfer clause near the end could fall outside the processed text.

For routing, select warranty-parse when the task is to extract stated terms from available warranty wording. Keep claim approval as a separate decision: matching “defects in materials” to a customer's reported fault still requires evidence about the product and the failure.

If transfer is allowed subject to proof of purchase, retain that clause beside the returned boolean. A true value alone can't carry the condition the next owner must meet.