Hugging Face Inference Endpoints vs Verda

Hugging Face Inference Endpoints

OAuth scopes separate reading endpoints from writing them, both OpenAPI documents are public, and the unauthenticated /v2/provider route lists every instance with its hourly price. An account needs a payment method and credits before the first deployment, no rate limits or SLA were found for the management API, and the docs price table disagrees with the live list in places.

Verda

The REST API has a public OpenAPI 3.1 document, a dated changelog, published rate limits with Retry-After, and an audit log endpoint. The CLI's MCP server refuses billed or destructive calls without confirm: true. Access needs a browser signup and a prepaid balance, credentials carry one scope, and instance creation has no idempotency key.

Hugging Face Inference Endpoints

1. Call GET https://api.endpoints.huggingface.cloud/v2/provider first and pick an instance whose status is available. The docs table lists types the API marks deprecated or not available
2. Send X-Scale-Up-Timeout: 600 on requests to an endpoint that scales to zero, or handle 503 while the first replica starts
3. Set scaleToZeroTimeout yourself. The docs give a default of 1 hour and the OpenAPI document says 15 minutes
4. Pause or delete an endpoint when the job is done. Billing covers every minute a replica is initialising or running
5. Give the agent a fine-grained token or the read-endpoints scope unless it must deploy. Endpoints are private by default and take the same Hugging Face token as a bearer

Verda

1. Exchange the client ID and secret at POST /v1/oauth2/token, then send the access token as a Bearer header. It expires after 3,600 seconds, so refresh it.
2. Send location_code on every create call. Requests without it have returned 400 since March 2026.
3. Call GET /v1/instance-availability before launching. POST /v1/instances returns 503 service_unavailable when the location has no capacity.
4. List instances before retrying a failed launch, because create has no idempotency key.
5. Use the delete action to stop charges. shutdown keeps billing, and deleted volumes stay recoverable for 96 hours unless delete_permanently is set.