13trust / 100

Glow Conflict Check

by GlowPulse in Other

x402 APIFailing, checked 4 h ago

Is retinol safe with vitamin C? Skincare ingredient-conflict checker — myth-vs-fact verdict on routine pairings (retinol+AHA, niacinamide+vitamin C, benzoyl peroxide+retinol), real pH/oxidation conflicts flagged separately from debunked myths, plus a layering-order suggestion.

GET
https://glowpulse.theaslangroupllc.com/api/glow/conflict-check
Price
$0.1
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
4 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 4 h ago: Amount "0.1" is not in atomic token units

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

How to call it

GET https://glowpulse.theaslangroupllc.com/api/glow/conflict-check

Each call costs $0.1 in USDC on Polygon, 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.

GET https://glowpulse.theaslangroupllc.com/api/glow/conflict-check?ingredients=retinol%2Cvitamin+c%2Cniacinamide

Parameters

ParameterTypeRequiredDescription
ingredientsstringNorequired — comma-separated ingredients or actives
langstringNoen | ko | ja | de | fr | es | pt (optional)

Example response

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

{
  "ingredients_checked": [
    "retinol",
    "vitamin c"
  ],
  "pairs_analyzed": [
    {
      "pair": [
        "retinol",
        "vitamin c"
      ],
      "verdict": "myth - safe to combine"
    }
  ]
}

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.1.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://glowpulse.theaslangroupllc.com/api/glow/conflict-check?ingredients=retinol%2Cvitamin+c%2Cniacinamide'

# 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 - 'https://glowpulse.theaslangroupllc.com/api/glow/conflict-check?ingredients=retinol%2Cvitamin+c%2Cniacinamide' \
  | 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.1 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.1" });
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.1 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fglowpulse.theaslangroupllc.com%2Fapi%2Fglow%2Fconflict-check
const res = await pay("https://glowpulse.theaslangroupllc.com/api/glow/conflict-check?ingredients=retinol%2Cvitamin+c%2Cniacinamide");
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.1 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.1"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://glowpulse.theaslangroupllc.com/api/glow/conflict-check?ingredients=retinol%2Cvitamin+c%2Cniacinamide")
    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 agoAmount "0.1" is not in atomic token units402298 ms$0.1
12 h agoAmount "0.1" is not in atomic token units402397 ms$0.1
20 h agoAmount "0.1" is not in atomic token units402244 ms$0.1
28 h agoAmount "0.1" is not in atomic token units402230 ms$0.1
37 h agoAmount "0.1" is not in atomic token units402302 ms$0.1
Show 10 older checks
45 h agoAmount "0.1" is not in atomic token units402272 ms$0.1
2 days agoAmount "0.1" is not in atomic token units402248 ms$0.1
3 days agoAmount "0.1" is not in atomic token units402231 ms$0.1
3 days agoAmount "0.1" is not in atomic token units402291 ms$0.1
3 days agoAmount "0.1" is not in atomic token units402283 ms$0.1
3 days agoAmount "0.1" is not in atomic token units402274 ms$0.1
4 days agoAmount "0.1" is not in atomic token units402217 ms$0.1
4 days agoAmount "0.1" is not in atomic token units402219 ms$0.1
4 days agoAmount "0.1" is not in atomic token units402238 ms$0.1
5 days agoAmount "0.1" is not in atomic token units402194 ms$0.1