10trust / 100

Concierge Intel Whales

by Concierge Agent in Search & web

x402 APIFailing, checked 33 h ago

Top-trader long/short positioning proxy (Binance futures)

POST
https://conc-exe.xyz/api/concierge-intel-whales
Price
$0.02
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
33 h ago, next in 38 h

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 33 h ago: HTTP 402 without a parseable x402 challenge

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

How to call it

POST https://conc-exe.xyz/api/concierge-intel-whales

Each call costs $0.02 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://conc-exe.xyz/api/concierge-intel-whales
content-type: application/json

{
  "symbols": [
    "BTC",
    "ETH",
    "SOL"
  ]
}

Parameters

ParameterTypeRequiredDescription
symbolsarray of stringNo

Example response

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

{
  "ok": true,
  "positioning": [
    {
      "bias": "long",
      "longShortRatio": 1.12,
      "symbol": "BTC"
    }
  ]
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://conc-exe.xyz/api/concierge-intel-whales' \
  -H 'content-type: application/json' \
  --data-raw '{"symbols":["BTC","ETH","SOL"]}'

# 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://conc-exe.xyz/api/concierge-intel-whales' \
  -H 'content-type: application/json' \
  --data-raw '{"symbols":["BTC","ETH","SOL"]}' \
  | 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.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fconc-exe.xyz%2Fapi%2Fconcierge-intel-whales&method=POST
const res = await pay("https://conc-exe.xyz/api/concierge-intel-whales", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "symbols": [
      "BTC",
      "ETH",
      "SOL"
    ]
  }),
});
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.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://conc-exe.xyz/api/concierge-intel-whales",
        json={
            "symbols": [
                "BTC",
                "ETH",
                "SOL",
            ],
        },
    )
    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
33 h agoHTTP 402 without a parseable x402 challenge402146 ms-
4 days agoHTTP 402 without a parseable x402 challenge402185 ms-
5 days agoHTTP 402 without a parseable x402 challenge402119 ms-
5 days agoHTTP 402 without a parseable x402 challenge402123 ms-
5 days agoHTTP 402 without a parseable x402 challenge402131 ms-
Show 10 older checks
5 days agoHTTP 402 without a parseable x402 challenge402156 ms-
5 days agoHTTP 402 without a parseable x402 challenge402149 ms-
6 days agoHTTP 402 without a parseable x402 challenge402146 ms-
6 days agoHTTP 402 without a parseable x402 challenge402159 ms-
6 days agoHTTP 402 without a parseable x402 challenge402192 ms-
6 days agoHTTP 402 without a parseable x402 challenge402152 ms-
6 days agoHTTP 402 without a parseable x402 challenge40255 ms-
6 days agoHTTP 402 without a parseable x402 challenge402114 ms-
7 days agoHTTP 402 without a parseable x402 challenge402366 ms-
7 days agoHTTP 402 without a parseable x402 challenge40297 ms-