Skip to content

Provider portal publishes orphaned service under API-key ID #1

Description

@Codecraft-Ops

Summary

A service created through the provider portal is published in public discovery, but it is not associated with the portal account for management, analytics, or earnings.

Reproduction

  1. Register a provider through /portal/register and verify the email.
  2. Create an External API service in the dashboard.
  3. The portal confirms: Your service "Base Contract Risk Report" is now live on the marketplace!.
  4. GET /api/v1/discover includes service 4a61ae34-b9f3-4c98-bef8-b50e84daa482 with status active.
  5. Refresh /portal/dashboard or open /portal/services.

Actual

  • Portal shows 0 active services, no services, 0 calls, and $0 revenue.
  • The public service record's provider_id is the account API-key ID (acf_ca2582cbaa864069).
  • A PAT generated from portal Settings resolves GET /api/v1/provider/dashboard to a different UUID provider (99af214b-ff65-4544-9b13-2888ff941c94) with 0 services.
  • A buyer-key smoke call through /api/v1/proxy/{service_id}/ succeeds (200, X-ACF-Free-Tier: true, usage ID returned), but neither portal nor PAT provider state records the service/call.

Expected

The portal create flow should persist the account's canonical provider UUID on the service (or dashboard queries should consistently join on API-key ID), so the service and its calls/earnings are manageable by the account that created it.

This blocks payout confidence: the service is publicly callable but the provider cannot observe or manage its attribution.

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