Dev Oauth Metadata
by oauth-server-metadata in Onchain & crypto
OAuth 2.0 authorization-server metadata (RFC 8414) with OpenID fallback: tries /.well-known/oauth-authorization-server then /.well-known/openid-configuration and returns the issuer, authorization/token/revocation/introspection/device endpoints, grant types, PKCE support, token auth methods, scopes, DPoP and PAR support. Also checks /.well-known/oauth-protected-resource for MCP-style resource metadata. $0.01 per server.
https://intel.rallylive.ca/dev/oauth-metadata- Price
- $0.01
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 52 ms
- 694 ms slowest 5%
- Last check
- Passed
- 10 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://intel.rallylive.ca/dev/oauth-metadata
Each call costs $0.01 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://intel.rallylive.ca/dev/oauth-metadata
content-type: application/json
{
"domain": "login.microsoftonline.com/common/v2.0"
}Example response
The provider's example. We can't check it without paying.
{
"authorization_endpoint": "https://…/authorize",
"grant_types": [
"authorization_code"
],
"issuer": "https://login.microsoftonline.com/common/v2.0",
"pkce": [
"S256"
],
"protected_resource_metadata": null,
"source": "openid-configuration",
"token_endpoint": "https://…/token"
}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.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://intel.rallylive.ca/dev/oauth-metadata' \
-H 'content-type: application/json' \
--data-raw '{"domain":"login.microsoftonline.com/common/v2.0"}'
# 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://intel.rallylive.ca/dev/oauth-metadata' \
-H 'content-type: application/json' \
--data-raw '{"domain":"login.microsoftonline.com/common/v2.0"}' \
| 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fintel.rallylive.ca%2Fdev%2Foauth-metadata&method=POST
const res = await pay("https://intel.rallylive.ca/dev/oauth-metadata", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"domain": "login.microsoftonline.com/common/v2.0"
}),
});
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://intel.rallylive.ca/dev/oauth-metadata",
json={
"domain": "login.microsoftonline.com/common/v2.0",
},
)
print(res.status_code, res.text)Security scan
1 finding
- Payment address changed recently in payment
Payment address changed from 0x91D568599fB802Cb3f03F067D2063785dBAF0abd to 0xFC24FD34da9e49A0110DCaEe3Ad30eC54175eBB3
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 10 h ago | Passed | 402 | 62 ms | $0.01 |
| 20 h ago | Passed | 402 | 161 ms | $0.01 |
| 31 h ago | Passed | 402 | 125 ms | $0.01 |
| 41 h ago | Passed | 402 | 192 ms | $0.01 |
| 2 days ago | Passed | 402 | 49 ms | $0.01 |
Show 10 older checks
| 3 days ago | Passed | 402 | 60 ms | $0.01 |
| 3 days ago | Passed | 402 | 107 ms | $0.01 |
| 3 days ago | Passed | 402 | 541 ms | $0.01 |
| 3 days ago | Passed | 402 | 50 ms | $0.01 |
| 3 days ago | Passed | 402 | 60 ms | $0.01 |
| 3 days ago | Passed | 402 | 50 ms | $0.01 |
| 4 days ago | Passed | 402 | 123 ms | $0.01 |
| 4 days ago | Passed | 402 | 93 ms | $0.01 |
| 4 days ago | Passed | 402 | 58 ms | $0.01 |
| 4 days ago | Passed | 402 | 44 ms | $0.01 |
History
| 11 Oct 2026 | Payment address changed from 0x91D568599fB802Cb3f03F067D2063785dBAF0abd to 0xFC24FD34da9e49A0110DCaEe3Ad30eC54175eBB3 |