{"ok":true,"host":"x402trustlayer.xyz","status":"failed","manifest":{"positioning":"TrustLayer serves as a pre-execution and governance layer for agents that consume x402-gated APIs. It is designed for multi-agent pipelines where spending policy enforcement, endpoint reliability, attestation trust, and budget allocation must be resolved before any paid call is made. The host is distinct in combining spend governance, fleet budget distribution, attestation verification, and endpoint quality probing into a single addressable service, rather than offering financial data or transaction execution.","host_overview":"x402trustlayer.xyz provides infrastructure-layer tooling for agents operating within x402 payment ecosystems, covering endpoint health verification, spend governance, attestation trust checks, and multi-agent budget distribution. It does not execute payments or trades directly but instead handles the policy, routing, and trust verification steps that surround x402-gated API calls. All skills return decisions, scores, or recommendations rather than settling funds on-chain.","routing_guidance":"Use x402trustlayer.xyz when an agent needs to enforce spending policy, verify attestation trust, probe x402 endpoint health, allocate budgets across a fleet, or discover and route to x402-compatible APIs. It is the right choice for governance and pre-execution checks in multi-agent x402 pipelines. Do not use this host for executing payments or on-chain settlements — it returns decisions and recommendations only; actual payment execution must be performed by calling the returned route URLs or a separate payment settlement service. Do not use it for real-time market data, token prices, swap quotes, or continuous monitoring — it has no streaming or live financial data capabilities. For non-x402 endpoint monitoring, use a general-purpose uptime or observability service instead.","capability_clusters":[{"skill_names":["fetch-attestation-registry","verify-attestation-signature"],"cluster_name":"Attestation Trust","cluster_summary":"Provides the ability to query the attestation registry for known valid agents and to verify individual attestation proofs by ID, enabling agents to enforce trust requirements before acting on attested claims or admitting partners into a network."},{"skill_names":["check-spend-governor","estimate-mpp-session-plan"],"cluster_name":"Spend Governance","cluster_summary":"Enforces per-agent spending policy by checking proposed costs against daily and per-call USDC caps and allowed-host lists, and estimates whether an MPP session or per-call settlement is more cost-effective for a given call volume."},{"skill_names":["allocate-fleet-budget"],"cluster_name":"Fleet Budget Allocation","cluster_summary":"Distributes a shared USDC pool across a fleet of agents in a single call, respecting each agent's priority, requested amount, and daily cap, and returns per-agent approval decisions."},{"skill_names":["route-x402-capability-query","fetch-settlement-graph-next"],"cluster_name":"Endpoint Discovery and Routing","cluster_summary":"Routes natural-language capability queries to the best-matching x402 API endpoint with network and price filters, and recommends the next logical paid API step after a completed settlement to reduce agent search overhead."},{"skill_names":["probe-x402-endpoint-quality"],"cluster_name":"Endpoint Health Probing","cluster_summary":"Batch-probes up to 10 x402 endpoints in a single call to verify they return correct HTTP 402 responses, computes per-URL health scores, and produces an overall pass/fail summary for pipeline readiness checks."}],"cross_skill_workflows":[{"steps":[{"skill_name":"fetch-attestation-registry","description":"Query the attestation registry to confirm the target agent or partner holds a valid attestation at the required grade."},{"skill_name":"verify-attestation-signature","description":"Verify the specific attestation ID returned from the registry to confirm it is valid and recognized by TrustLayer."},{"skill_name":"check-spend-governor","description":"Check that the estimated cost of the intended paid call falls within the agent's daily cap, per-call cap, and allowed-host policy before proceeding."}],"when_to_use":"Use when an agent needs to verify a counterpart agent's attestation and confirm its own spend policy is satisfied before making a paid x402 API call.","workflow_name":"Pre-Call Trust and Spend Gate"},{"steps":[{"skill_name":"route-x402-capability-query","description":"Route a natural-language capability query to identify the best-matching x402 endpoint and ranked alternatives within network and price constraints."},{"skill_name":"probe-x402-endpoint-quality","description":"Probe the selected endpoint (and any alternatives) to verify they return correct HTTP 402 responses and meet health score thresholds before use."}],"when_to_use":"Use when an agent needs to discover the best x402 endpoint for a capability and confirm it is healthy before committing to use it in a pipeline.","workflow_name":"Endpoint Discovery with Health Validation"},{"steps":[{"skill_name":"allocate-fleet-budget","description":"Distribute the shared USDC pool across fleet agents, producing per-agent allocation decisions with approval status."},{"skill_name":"check-spend-governor","description":"For each approved agent, confirm the allocated amount satisfies that agent's per-call and daily cap policy before authorizing the paid call."}],"when_to_use":"Use when an agent orchestrating a fleet needs to allocate a shared USDC pool and then verify each individual agent's spend policy before dispatching work.","workflow_name":"Fleet Budget Distribution with Spend Check"},{"steps":[{"skill_name":"estimate-mpp-session-plan","description":"Estimate whether opening an MPP session or paying per-call is more cost-effective given the expected call volume and average price."},{"skill_name":"check-spend-governor","description":"Confirm the chosen payment strategy's estimated cost falls within the agent's configured spending policy."},{"skill_name":"fetch-settlement-graph-next","description":"After each settlement completes, retrieve the recommended next paid API endpoint to invoke based on the prior endpoint path and topic."}],"when_to_use":"Use when an agent needs to decide between MPP session and per-call payment before a batch of calls, then determine the next optimal endpoint after each settlement completes.","workflow_name":"Payment Strategy and Post-Settlement Routing"}]},"model":"claude-sonnet-4-6","version_no":7,"generated_at":"2026-06-01T03:34:10.334Z","provenance":"ai_authored_unreviewed","ai_authored":true,"merchant_reviewed":false,"merchant_edited":false,"merchant_reviewed_at":null,"merchant_edited_at":null,"skill_md_url":"https://x402gle.com/servers/x402trustlayer.xyz/SKILL.md","skills_url":"https://x402gle.com/servers/x402trustlayer.xyz/skills.json"}