TradePulse

What the provider says

Quoted from x402 Bazaar · source record · read 2026-10-25

Facts and where they come from

Price

0.1 USDC per call Provider claim

Recorded value: 0.15 USDC per call.

Unit

per call

Protocol

x402, REST · transport: HTTP Provider claim

Auth

x402

Endpoint

https://tradepulse.theaslangroupllc.com/api/trade/incoterms

Source

x402 Bazaar (Coinbase CDP) · Public discovery API (provider-published records)

Last checked

Not checked by us yet — the data is as the source published it

First seen

2026-10-24

Usage

1 calls · 1 unique payers in the 30 days before 2026-10-24. Measured by the x402 Bazaar, not by us and not by the provider.

Payments and earnings

No settled payment on record. Earnings for this service are unknown — not zero. The source counts 1 calls in 30 days, which at the published price is roughly $0.10 of activity. Activity is not revenue; no charge has been reconciled for it.

Payment rails

A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it. See evidence levels.

Input and output, as published

Request

{
    "method": "GET",
    "queryParams": {
        "from_country": "seller/exporting country for corridor-specific context (optional)",
        "lang": "en | es | fr | de | ja | pt | zh | ko | ar (default: en)",
        "product": "product type for transport-mode guidance (optional)",
        "term": "(required) Incoterms 2020 rule \u2014 one of: EXW, FCA, FAS, FOB, CFR, CIF, CPT, CIP, DAP, DPU, DDP",
        "to_country": "buyer/importing country for corridor-specific context (optional)"
    },
    "type": "http"
}

Response

{
    "errors": {
        "400": {
            "description": "Invalid or missing parameter(s). Returned before the payment gate on paid requests, so a malformed call is never charged. JSON body: { error: <what is wrong and how to fix it> } plus usage hints.",
            "example": {
                "error": "invalid request"
            }
        },
        "402": {
            "description": "Payment required \u2014 x402 v2 challenge; the accepts array lists scheme, network, and amount. Retry the same request with a PAYMENT-SIGNATURE (v2) or X-PAYMENT (v1) header. Verification is free."
        },
        "500": {
            "description": "Unexpected server error. If a payment settled without a usable result, contact info@theaslangroupllc.com with the settlement tx hash for a re-run or credit.",
            "example": {
                "error": "upstream_failed"
            }
        }
    },
    "example": {
        "buyer_obligations": {
            "pays_for": [
                "Ocean freight",
                "Marine insurance",
                "Import duties"
            ]
        },
        "full_name": "Free on Board",
        "risk_transfer_point": "When goods pass ship's rail at named port of origin",
        "seller_obligations": {
            "pays_for": [
                "Export customs",
                "Origin port handling to vessel"
            ]
        },
        "term": "FOB",
        "when_NOT_to_use": [
            "Container shipments \u2014 use FCA instead (ICC 2020 recommendation)"
        ]
    },
    "type": "json"
}

Examples are the provider's own, not a call we made.

Provenance

One row per statement. “Verified” means we checked it ourselves and the finding is quoted. “Provider claim” means we read it in the provider's own record. “Not found” is a statement about our search, not proof of absence.

Endpoint checks

We have not called this endpoint yet. Until we do, everything above is what the source published — no more.

Tags