x402 Eligibility Checker

Store Positioning

Store title: x402 Eligibility Checker

Short description: Check whether an actor/tool configuration appears ready for x402-style agentic payment eligibility by auditing pricing, permissions, standby mode, schema clarity, and event configuration.

SEO title: x402 Eligibility Checker — API, schema, and developer QA

SEO description: Check whether an actor/tool configuration appears ready for x402-style agentic payment eligibility by auditing pricing, permissions, standby mode, schema clarity, and event configuration. Use it to catch contract drift, schema mistakes, unsafe endpoint assumptions, and developer-tool quality issues before release.

Categories: SEO_TOOLS, DEVELOPER_TOOLS

Keywords: x402, eligibility, checker, schema, pricing audit, api/developer qa

Pay-Per-Event Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

• Tier: A1 — API/developer QA
• Primary event: operation-tested at $0.00650 base
• Default max charge: $10.00
• Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

• actor-start: base $0.00500, GOLD $0.00400. X402 Eligibility Checker: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• operation-tested: base $0.00650, GOLD $0.00520. X402 Eligibility Checker: charged when operation tested is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• contract-rule-checked: base $0.00390, GOLD $0.00312. X402 Eligibility Checker: charged when contract rule checked is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• report-generated: base $0.05000, GOLD $0.04000. X402 Eligibility Checker: charged when report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

The actor accepts actor-start before work, accepts the primary event before each dataset row, and accepts report-generated before writing report files. If maxChargeUsd or the live PPE limit blocks a charge, the corresponding row or report is not written.

Public Task Concepts

• Audit x402 Eligibility controls on a capped public sample
• Find high-priority x402 Eligibility issues before release
• Validate x402 Eligibility evidence from supplied pages
• Prioritize x402 Eligibility fixes with severity and proof
• Export x402 Eligibility QA rows for client review Audit actor metadata for x402-style agentic payment readiness.

What It Does

Checks PPE pricing, Standby usage, broad permissions, schema clarity, README readiness, and public task availability.

Inputs

This actor exposes these input fields in .actor/input_schema.json:

• actorConfigJson
• actorMetadataJson
• pricingConfigJson
• readmeText
• inputSchemaJson
• datasetSchemaJson
• strictMode
• maxChargeUsd

The exact default audits the real local public configuration, pricing, README, input schema, dataset schema, and five task definitions for openapi-response-validator at the current committed source tip; it contains no credentials.

Outputs

Dataset rows contain:

• actorSlug
• checkName
• checkStatus
• requirementCategory
• evidence
• severity
• fixHint
• eligibilityImpact
• overallEligibility

Sample outputs in examples/output.sample.json and output.sample.json were generated from examples/input.tiny.json through actor logic.

Reports

After the report-generated charge is accepted, the actor writes its Markdown, JSON, or CSV reports to the key-value store. A rejected report charge leaves those files unwritten.

Public Task Concepts

• Validate x402 Eligibility Checker before release
• Run a bounded x402 Eligibility Checker QA check
• Generate developer QA evidence for x402 Eligibility Checker

Safe use

Use small capped runs first. Network paths are bounded; review output quality and costs before increasing limits.