Live Palladium Price SkillLive Palladium Price Skill

OnlineCredit Usage:1 per callTool:LivePalladiumPriceSkill

The tool

Give your agent the spot price of palladium. Call it as an MCP tool to read live palladium prices in any currency and unit — updated in real time.

Once your client is connected to the VerveKit MCP server, this appears in its tool list as LivePalladiumPriceSkill. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.

Tool call
{
  "name": "LivePalladiumPriceSkill",
  "arguments": {}
}

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.

Client config
{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}
Endpoint
https://api.vervekit.com/v1/mcp

Per-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made.

ArgumentTypeExampleDescription
currencyPremiumstringUSDThe currency to get the price in
hourlyPremiumbooleantrueInclude hourly price data for the past 24 hours

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "currency": "USD",
    "gram": 40.08,
    "kilogram": 40075.88,
    "ounce": 1246.5,
    "lastUpdated": "2026-02-07T12:00:00.000Z",
    "change24h": -8.2,
    "change24hPct": -0.65,
    "changeDirection": "down",
    "high24h": 1259,
    "low24h": 1241.1,
    "formatted": {
      "ounce": "$1,246.50",
      "gram": "$40.08",
      "kilogram": "$40,075.88",
      "ounceWords": "one thousand, two hundred forty-seven dollars",
      "kilogramWords": "forty thousand, seventy-six dollars"
    }
  }
}

Fields

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.
FieldTypeExampleDescription
currencystringUSDISO 4217 currency code for price values
gramnumber40.08Palladium price per gram in specified currency
kilogramnumber40075.88Palladium price per kilogram in specified currency
ouncenumber1246.5Palladium price per troy ounce in specified currency
lastUpdatedstring2026-02-07T12:00:00.000ZISO 8601 timestamp of last price update
change24hnumber-8.2Price change vs 24 hours ago in currency units
change24hPctPremiumnumber-0.65Percentage price change vs 24 hours ago
changeDirectionstringdownDirection of 24h change: up, down, or unchanged
high24hPremiumnumber1259Highest price in the past 24 hours
low24hPremiumnumber1241.1Lowest price in the past 24 hours
formattedobject{…}
formatted.ouncePremiumstring$1,246.50Formatted ounce price with currency symbol
formatted.gramPremiumstring$40.08Formatted gram price with currency symbol
formatted.kilogramPremiumstring$40,075.88Formatted kilogram price with currency symbol
formatted.ounceWordsPremiumstringone thousand, two hundred forty-seven dollarsOunce price spelled out in words with currency
formatted.kilogramWordsPremiumstringforty thousand, seventy-six dollarsKilogram price spelled out in words with currency

Failure modes

Errors come back as tool errors with a sentence the model can act on, not a bare status code.

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This skill isn't part of VerveKit. Check the catalog.
429Brief rate limit. Retrying after a moment succeeds.

Other ways to use Live Palladium Price Skill

Set up Live Palladium Price Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an X-API-Key header, with SDKs for Node, Python and .NET.APIVerveReference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContextReference →

Frequently asked questions

Do I have to tell the agent to use LivePalladiumPriceSkill?

No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.

Does connecting the server expose every tool at once?

Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.

What does a call cost?

1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.

Is there a REST version of this?

Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?