Skip to content

REST submissions drop price_usdc during approval #1

Description

@fablerlabs

The public POST /api/v1/submit schema accepts price_usdc, but the approval path stores only price_min_usdc / price_max_usdc:

  • directory/routes.py::SubmissionPayload defines price_usdc.
  • directory/jobs.py::_approve assigns price_min = p.get("price_min_usdc") and price_max = p.get("price_max_usdc").
  • The REST payload is passed through without normalizing that field.

Live reproduction: submission #64 / service x402-fablerlabs-com-sub64 was sent with price_usdc: 0.005 and auto-verified against a v2 challenge advertising 5,000 atomic USDC. Its service card and unified resource record currently have price_hint: null, and budget-filtered broker recommendations omit it.

Expected: a REST submission's price_usdc should populate both stored price bounds, or the verified x402 amount should override the submitted value.

There is also no public update route once origin dedupe returns already_listed. For this affected record, the intended description begins "Web scraping and HTML-to-text for one public HTTPS page..." so it can match the same intent as the endpoint it exposes.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions