Orocle Xactum
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XACTUM_ACCEPT_TERMS | Yes | Set to "true" to accept https://api.xactum.com/terms as a business. | |
| XACTUM_BUSINESS_USE | Yes | Set to "true" to confirm business use. | |
| XACTUM_PAYER_PRIVATE_KEY | Yes | Private key of the payer wallet (e.g. 0x…) used to pay the 0.03 USDC per-query fee on Base via x402. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| xactum_verify_priceA | Before paying for or committing to an LLM model/price: check whether a quoted or paid per-token price is competitive against an independent reference. Costs 0.03 USDC (x402, Base); inconclusive answers are free. XACTUM verifies, never routes, and takes no referral fees. |
| xactum_verify_modelA | After an LLM call: check whether the model actually served is consistent with the model claimed, using call metadata only (never prompts or outputs). Costs 0.03 USDC (x402, Base); inconclusive answers are free. |
| xactum_feedbackB | Free: rate a XACTUM answer with its queryId (structured, no free text). A valid review earns a small credit for the given wallet. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools target clearly distinct actions: verifying served-model consistency, verifying price competitiveness, and submitting structured feedback. An agent can unambiguously pick the right tool based on intent, and the descriptions reinforce the boundaries.
All tools share the xactum_ prefix, and the two verification tools follow a clean verify_<noun> pattern. xactum_feedback deviates slightly by using a bare noun rather than a verb_noun form, but it remains readable and predictable.
Three tools is on the thin side but fits a narrow verification-oracle service: model verification, price verification, and feedback each earn their place. It is slightly under-scoped rather than bloated.
The core verify-and-feedback loop is covered, but there is a notable gap: feedback earns wallet credit yet no tool lets an agent check a credit balance, redeem it, or retrieve past verification results. Agents will hit a dead end after earning credit.