Concierge Intel Macro
by Concierge Agent in Markets & finance
Macro snapshot — SPX, VIX, DXY, gold, BTC/ETH marks, Fear & Greed, Treasury yields, central-bank calendar
https://conc-exe.xyz/api/concierge-intel-macro- Price
- $0.02
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 3 days ago, next any minute now
Reliability
Latest check failed 3 days 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-macro
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-macro
content-type: application/json
{}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
message | string | No | Optional context for logging |
Example response
The provider's example. We can't check it without paying.
{
"macro": {
"upcomingEvents": [
{
"label": "FOMC decision",
"when": "2026-03-18"
}
]
},
"marks": [
{
"change24h": "+0.42%",
"price": "5,240.10",
"symbol": "SPX"
}
],
"ok": true,
"sentiment": {
"index": 62,
"label": "Greed"
}
}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-macro' \
-H 'content-type: application/json' \
--data-raw '{}'
# 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-macro' \
-H 'content-type: application/json' \
--data-raw '{}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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-macro&method=POST
const res = await pay("https://conc-exe.xyz/api/concierge-intel-macro", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({}),
});
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-macro",
json={},
)
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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 days ago | HTTP 402 without a parseable x402 challenge | 402 | 334 ms | - |
| 4 days ago | HTTP 402 without a parseable x402 challenge | 402 | 158 ms | - |
| 4 days ago | HTTP 402 without a parseable x402 challenge | 402 | 153 ms | - |
| 4 days ago | HTTP 402 without a parseable x402 challenge | 402 | 143 ms | - |
| 4 days ago | HTTP 402 without a parseable x402 challenge | 402 | 151 ms | - |
Show 10 older checks
| 4 days ago | HTTP 402 without a parseable x402 challenge | 402 | 128 ms | - |
| 4 days ago | HTTP 402 without a parseable x402 challenge | 402 | 118 ms | - |
| 5 days ago | HTTP 402 without a parseable x402 challenge | 402 | 122 ms | - |
| 5 days ago | HTTP 402 without a parseable x402 challenge | 402 | 246 ms | - |
| 5 days ago | HTTP 402 without a parseable x402 challenge | 402 | 164 ms | - |
| 5 days ago | HTTP 402 without a parseable x402 challenge | 402 | 121 ms | - |
| 5 days ago | HTTP 402 without a parseable x402 challenge | 402 | 132 ms | - |
| 6 days ago | HTTP 402 without a parseable x402 challenge | 402 | 154 ms | - |
| 6 days ago | HTTP 402 without a parseable x402 challenge | 402 | 142 ms | - |
| 6 days ago | HTTP 402 without a parseable x402 challenge | 402 | 53 ms | - |