Roundhouse AI

api.syntalic.com

Marketing/competitive analysis query - $0.01 per request

TradingLiveeip155:8453Exactvia facilitator:payAI
https://api.syntalic.com/v1/marketing/availability-index
Settlements · 30d
139↑ 259%
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days.
$11.72
Verified settled volume
897 settlements proven x402 by their on-chain EIP-3009 marker.
$0.010
Listed price
As published in the catalog. Always read the live 402 before paying.
—
Calls · 30d
Upstream's own call count for this endpoint, not ours.
—
Unique payers · 30d
Never called
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0xe2e662cF219025AFC0C9Bf850b6a2B0a0b5517fe

The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.

Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Provider

The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.

Accepts

The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.

0.01USDC≈ $0.01 USD
on Base · exact scheme

Pay 0.01 USDC on Base to 0xe2e6…517fe. The signed payment is good for 5 minutes.

Paid to
0xe2e6…517fe
USD Coin contract
0x8335…02913
Payment window
5 minutes
As published
10000 smallest units
The catalog’s raw entry
[
  {
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "extra": {
      "name": "USD Coin",
      "version": "2"
    },
    "payTo": "0xe2e662cF219025AFC0C9Bf850b6a2B0a0b5517fe",
    "amount": "10000",
    "scheme": "exact",
    "network": "eip155:8453",
    "maxTimeoutSeconds": 300
  }
]

Extensions

{
  "bazaar": {
    "info": {
      "input": {
        "type": "http",
        "method": "GET",
        "queryParams": {
          "category": "food-beverages-tobacco/beverages/soda"
        }
      },
      "output": {
        "type": "json"
      }
    },
    "schema": {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "input"
      ],
      "properties": {
        "input": {
          "type": "object",
          "required": [
            "type",
            "method"
          ],
          "properties": {
            "type": {
              "type": "string",
              "const": "http"
            },
            "method": {
              "enum": [
                "GET",
                "HEAD",
                "DELETE"
              ],
              "type": "string"
            },
            "headers": {
              "type": "object",
              "additionalProperties": {
                "type": "string"
              }
            },
            "queryParams": {
              "type": "object",
              "properties": {
                "brand": {
                  "type": "string",
                  "example": "Apple",
                  "minLength": 1,
                  "description": "Brand name (e.g., Sony, Samsung, Nike)"
                },
                "country": {
                  "enum": [
                    "us",
                    "ca"
                  ],
                  "type": "string",
                  "default": "us",
                  "example": "us",
                  "description": "Country (us or ca)"
                },
                "category": {
                  "type": "string",
                  "example": "electronics",
                  "minLength": 1,
                  "description": "Product category in the Shopify product taxonomy. Accepts a display path (e.g. 'Electronics > Computers > Laptops'), its slug form (e.g. 'electronics/computers/laptops'), a single path segment (e.g. 'laptops', 'headphones'), or an everyday shelf name (e.g. 'apparel', 'beauty', 'grocery'); matched against the catalog's category tree (exact node, subtree, or whole path segment). Also accepts a GS1 GPC code (exactly 8 digits, e.g. '10001159') to filter by PRODUCT TYPE instead of by shelf placement — the same product type is shelved under different categories by different retailers, so a category filter answers from a fraction of the data while a GPC code spans them. Coarser codes (class/family/segment) match every brick beneath them. Resolve a phrase to a code with /v1/reference/classify?q=... ; when a code is used, resolved.match_source is 'gpc'."
                },
                "aggregate_by": {
                  "enum": [
                    "seller",
                    "category_root"
                  ],
                  "type": "string",
                  "default": "seller",
                  "description": "Dimension to group by: retail chain (default) or category root."
                }
              },
              "additionalProperties": false
            }
          },
          "additionalProperties": false
        },
        "output": {
          "type": "object",
          "required": [
            "type"
          ],
          "properties": {
            "type": {
              "type": "string"
            },
            "example": {
              "type": "object"
            }
          }
        }
      }
    }
  }
}

Provenance

Seen in the source catalog
2026-09-23 11:42Z
Last indexed by Roundhouse
2026-09-24 11:45Z
Last enriched (probe, favicon, geo)
2026-09-18 21:15Z
x402 version
2
Max timeout
300s
Liveness probe
HTTP 400
Report

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.

GET api.roundhouseai.io/v0/endpoints

No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days. Verified volume counts only settlements with an on-chain EIP-3009 marker.

Open skill.md
Show the prompt
Using Roundhouse, look up the x402 service api.syntalic.com and tell me whether it is
worth paying: what a call costs, whether the endpoint answered when last probed, and what
its payment record actually shows.

curl -s 'https://api.roundhouseai.io/v0/endpoints?q=api.syntalic.com'
curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>'

Then call it: read the price from the live 402 at https://api.syntalic.com/v1/marketing/availability-index, never from
a cached figure, and pay with an x402 client.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.