Skip to main content
A provider offer lets you serve an existing Tulip model market and earn its canonical credits. You operate the endpoint and choose your own tariff and payout address.
Hugging Face Inference Endpoints are the supported provider infrastructure in v1. Tulip is designed to add other endpoint vendors and GPU networks in later versions.

​
Prerequisites

  • An active Tulip model market.
  • The exact pinned model revision deployed to a Hugging Face Inference Endpoint.
  • An HTTPS endpoint beneath endpoints.huggingface.cloud.
  • A Hugging Face endpoint token.
  • A Robinhood Chain wallet for the provider operator.
Provider onboarding with a verified model Select a launched model, verify its identity, and configure provider routing and pricing.

​
Register an offer

1

Inspect the endpoint

Send the model ID, endpoint URL, and endpoint token to the Gateway inspection route. Tulip validates the origin, discovers OpenAPI capabilities, and calculates the manifest commitments.
2

Register on-chain

In Tulip’s provider registration flow, enter the model ID, payout address, returned commitments, and initial tariff. Confirm the prepared transaction from the operator wallet.
3

Prove operator control

Request an expiring EIP-712 registration challenge from the Gateway and sign it with the on-chain operator wallet. Registration nonces cannot be replayed.
4

Store private endpoint access

Submit the signature, offer ID, endpoint URL, and token to the Gateway registration route. The Gateway verifies that the endpoint matches the on-chain commitments.
5

Verify availability

Refresh offer verification and confirm that the public model catalog reports an active provider. Verification expires after 15 minutes and is refreshed during routing when needed.

​
Set a tariff

You may set any non-zero combination of input rate, output rate, minimum charge, and wake fee that passes the contract’s tariff validation. Rates are denominated in credit base units per one million tokens. Tariff changes use two transactions:
  1. Submit the new tariff from the provider controls to create a pending version.
  2. Return after the displayed protocol delay and activate the pending version.
Receipts remain bound to the tariff version effective when inference started.

​
Provider revenue

At settlement, the escrow transfers the provider share to the offer’s current payout address. For example, with a 5% protocol share and a 2% creator share, the selected provider receives 93% of the charged credits. Providers receive credits, not USDG. See Fees for the complete fee model.

​
Operations

  • Keep endpoint usage reporting enabled. Tulip rejects responses that omit usage.
  • Keep the registered endpoint manifest and capability commitment synchronized.
  • Pause the offer before planned downtime.
  • Update the payout address from the operator wallet when rotating treasury infrastructure.
  • Treat Hugging Face credentials and database encryption keys as secrets.