ToolVet
80trust / 100

Schema Parse Extract

by NetIntel in Search & web

x402 APIPassing, checked 4 h ago

Extract structured data from any unstructured text into your own JSON Schema — structured-data / information extraction, text-to-JSON, LLM data enrichment. You supply the schema; the LLM returns a matching object. Works for contacts, invoices, events, product specs, medical records, legal clauses, resumes — any shape. Returns the extracted object plus token usage; unfound fields are omitted or null.

POST
https://netintel.dev/schema-parse/extract
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
292 ms
464 ms slowest 5%
Last check
Passed
4 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://netintel.dev/schema-parse/extract

Each call costs $0.01 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://netintel.dev/schema-parse/extract
content-type: application/json

{
  "raw_text": "Hi I'm Sarah Chen, VP of Engineering at Acme Corp. Reach me at [email protected] or 555-867-5309.",
  "target_schema": {
    "properties": {
      "company": {
        "type": "string"
      },
      "email": {
        "type": "string"
      },
      "name": {
        "type": "string"
      },
      "phone": {
        "type": "string"
      },
      "role": {
        "type": "string"
      }
    },
    "required": [
      "name",
      "email"
    ],
    "type": "object"
  }
}

Parameters

ParameterTypeRequiredDescription
raw_textstringYesUnstructured text to extract data from — emails, resumes, articles, log entries, contracts, support tickets, etc.
target_schemaobjectYesA standard JSON Schema object with type, properties, and optionally required. Defines the shape of the extracted output.

Example response

The provider's example. We can't check it without paying.

{
  "extracted": {
    "company": "Acme Corp",
    "email": "[email protected]",
    "name": "Sarah Chen",
    "phone": "555-867-5309",
    "role": "VP of Engineering"
  },
  "tokens_used": {
    "input": 312,
    "output": 48
  }
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://netintel.dev/schema-parse/extract' \
  -H 'content-type: application/json' \
  --data-raw '{"raw_text":"Hi I'\''m Sarah Chen, VP of Engineering at Acme Corp. Reach me at [email protected] or 555-867-5309.","target_schema":{"properties":{"company":{"type":"string"},"email":{"type":"string"},"name":{"type":"string"},"phone":{"type":"string"},"role":{"type":"string"}},"required":["name","email"],"type":"object"}}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://netintel.dev/schema-parse/extract' \
  -H 'content-type: application/json' \
  --data-raw '{"raw_text":"Hi I'\''m Sarah Chen, VP of Engineering at Acme Corp. Reach me at [email protected] or 555-867-5309.","target_schema":{"properties":{"company":{"type":"string"},"email":{"type":"string"},"name":{"type":"string"},"phone":{"type":"string"},"role":{"type":"string"}},"required":["name","email"],"type":"object"}}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fnetintel.dev%2Fschema-parse%2Fextract&method=POST
const res = await pay("https://netintel.dev/schema-parse/extract", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "raw_text": "Hi I'm Sarah Chen, VP of Engineering at Acme Corp. Reach me at [email protected] or 555-867-5309.",
    "target_schema": {
      "properties": {
        "company": {
          "type": "string"
        },
        "email": {
          "type": "string"
        },
        "name": {
          "type": "string"
        },
        "phone": {
          "type": "string"
        },
        "role": {
          "type": "string"
        }
      },
      "required": [
        "name",
        "email"
      ],
      "type": "object"
    }
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://netintel.dev/schema-parse/extract",
        json={
            "raw_text": "Hi I'm Sarah Chen, VP of Engineering at Acme Corp. Reach me at [email protected] or 555-867-5309.",
            "target_schema": {
                "properties": {
                    "company": {
                        "type": "string",
                    },
                    "email": {
                        "type": "string",
                    },
                    "name": {
                        "type": "string",
                    },
                    "phone": {
                        "type": "string",
                    },
                    "role": {
                        "type": "string",
                    },
                },
                "required": [
                    "name",
                    "email",
                ],
                "type": "object",
            },
        },
    )
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
4 h agoPassed402296 ms$0.01
9 h agoPassed402180 ms$0.01
13 h agoPassed402361 ms$0.01
17 h agoPassed402286 ms$0.01
21 h agoPassed402464 ms$0.01
Show 10 older checks
26 h agoPassed402264 ms$0.01
30 h agoPassed402248 ms$0.01
34 h agoPassed402314 ms$0.01
38 h agoPassed402402 ms$0.01
43 h agoPassed402182 ms$0.01
47 h agoPassed402460 ms$0.01
2 days agoPassed402421 ms$0.01
2 days agoPassed402286 ms$0.01
2 days agoPassed402543 ms$0.01
3 days agoPassed402313 ms$0.01