remove mention of 'direct calls'

Author: burtenshaw

docs/inference-providers/pricing.md

@@ -22,20 +22,19 @@ Your monthly credits automatically apply when you route requests through Hugging
 
 Inference Providers offers flexibility in how you're billed. Understanding these options upfront helps you choose the best approach for your needs:
 
-| Feature | **Routed by Hugging Face** | **Custom Provider Key** | **Direct Calls** |
-| :--- | :--- | :--- | :--- |
-| **How it Works** | Your request routes through HF to the provider | You set a custom provider key in HF settings | You provide the provider key directly in your code |
-| **Billing** | Pay-as-you-go on your HF account | Billed directly by the provider | Billed directly by the provider |
-| **Monthly Credits** | **✅ Yes** - Credits apply to eligible providers | **❌ No** - Credits don't apply | **❌ No** - Credits don't apply |
-| **Provider Account Needed** | **❌ No** - We handle everything | **✅ Yes** - You need provider accounts | **✅ Yes** - You need provider accounts |
-| **Best For** | Simplicity, experimentation, consolidated billing | More billing control, using non-integrated providers | Full control, bypassing HF routing |
-| **Integration** | SDKs, Playground, widgets, Data AI Studio | SDKs, Playground, widgets, Data AI Studio | SDKs only |
+| Feature | **Routed by Hugging Face** | **Custom Provider Key** |
+| :--- | :--- | :--- |
+| **How it Works** | Your request routes through HF to the provider | You set a custom provider key in HF settings |
+| **Billing** | Pay-as-you-go on your HF account | Billed directly by the provider |
+| **Monthly Credits** | **✅ Yes** - Credits apply to eligible providers | **❌ No** - Credits don't apply |
+| **Provider Account Needed** | **❌ No** - We handle everything | **✅ Yes** - You need provider accounts |
+| **Best For** | Simplicity, experimentation, consolidated billing | More billing control, using non-integrated providers |
+| **Integration** | SDKs, Playground, widgets, Data AI Studio | SDKs, Playground, widgets, Data AI Studio |
 
 ### Which Option Should I Choose?
 
 - **Start with Routed by Hugging Face** if you want simplicity and to use your monthly credits
 - **Use Custom Provider Key** if you need specific provider features or you're consistently using the same provider
-- **Use Direct Calls** if you want to bypass Hugging Face routing entirely
 
 ## Pay-as-you-Go Details
 
@@ -56,23 +55,20 @@ Hugging Face charges you the same rates as the provider, with no additional fees
 
 You can track your spending anytime on your [billing page](https://huggingface.co/settings/billing).
 
-## Routed Requests vs Direct Calls (Detailed Comparison)
+## Hugging Face Billing vs Custom Provider Key (Detailed Comparison)
 
 The documentation above assumes you are making routed requests to external providers. In practice, there are 3 different ways to run inference, each with unique billing implications:
 
 - **Routed Request**: This is the default method for using Inference Providers. Simply use the JavaScript or Python `InferenceClient`, or make raw HTTP requests with your Hugging Face User Access Token. Your request is automatically routed through Hugging Face to the provider's platform. No separate provider account is required, and billing is managed directly by Hugging Face. This approach lets you seamlessly switch between providers without additional setup.
 
 - **Routed Request with Custom Key**: In your [settings page](https://huggingface.co/settings/inference-providers) on the Hub, you can configure a custom key for each provider. To use this option, you'll need to create an account on the provider's platform, and billing will be handled directly by that provider. Hugging Face won't charge you for the call. This method gives you more control over billing when experimenting with models on the Hub. When making a routed request with a custom key, your code remains unchanged—you'll still pass your Hugging Face User Access Token. Hugging Face will automatically swap the authentication when routing the request.
 
-- **Direct Calls**: If you provide a custom key when using the JavaScript or Python `InferenceClient`, the call will be made directly to the provider's platform. Billing is managed by the provider, and Hugging Face is not notified of the request. This option is ideal if you want to use the unified `InferenceClient` interface without routing through Hugging Face.
-
 Here is a table that sums up what we've seen so far:
 
 |                                    | HF routing | Billed by    | Free-tier included | Pay-as-you-go                                   | Integration                               |
 | ---------------------------------- | ---------- | ------------ | ------------------ | ----------------------------------------------- | ----------------------------------------- |
 | **Routed request**                 | Yes        | Hugging Face | Yes                | Only for PRO users and for integrated providers | SDKs, Playground, widgets, Data AI Studio |
 | **Routed request with custom key** | Yes        | Provider     | No                 | Yes                                             | SDKs, Playground, widgets, Data AI Studio |
-| **Direct call**                    | No         | Provider     | No                 | Yes                                             | SDKs only                                 |
 
 ## HF-Inference cost
 
@@ -82,7 +78,7 @@ For instance, a request to [black-forest-labs/FLUX.1-dev](https://huggingface.co
 
 The `"hf-inference"` provider is currently the default provider when working with the JavaScript and Python SDKs. Note that this default might change in the future.
 
-## Billing forEnterprise Hub organizations
+## Billing for Enterprise Hub organizations
 
 For Enterprise Hub organizations, it is possible to centralize billing for all of your users. Each user still uses their own User Access Token but the requests are billed to your organization. This can be done by passing `"X-HF-Bill-To: my-org-name"` as a header in your HTTP requests.