What authentication does the DfShop API use?

The DfShop API authenticates with an API key, which you can send either in the `X-DfApi-Token` header or as a `token` query parameter, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

Can I create and update orders with the DfShop API?

Yes. The DfShop API lists orders, retrieves a single order by its id, creates a new order, and updates an existing one. You can read product and inventory data alongside orders to confirm availability before an order is placed.

What are the rate limits for the DfShop API?

The OpenAPI spec does not specify rate limits for the DfShop API. Check the provider's documentation at https://dfshop.com for the current limits that apply to your token.

Can I limit what my agent is allowed to do with the DfShop API?

Yes. Order and product ids travel in the URL path, so a rule can scope your agent to specific orders or products. Write a rule that allows only the read operations, such as listing products and checking inventory, and leave order creation and updates out unless the agent needs them, and every call it makes is logged.

How do I process orders with the DfShop API through Jentic?

Search Jentic for 'create an order in my shop' and it returns the DfShop create-order operation with its input schema. Import the DfShop API from the Jentic API Directory, store your API token once, and your agent can list, create, and update orders without hand-wiring the token on each request.

Is there a DfShop API MCP server?

You don't need an MCP server to give your agent the DfShop API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the product, inventory, and order operations. Nothing extra loads into the agent's context until an operation is actually used.