canonical: https://jentic.com/apis/apisemparar.com.br/apisemparar # Apisemparar Pedido Varejo Digital The Sem Parar Retail Orders API handles digital retail ordering for the Sem Parar network. It registers and validates a customer, validates a vehicle plate, and then creates, finalizes, and checks the status of a retail order. Supporting operations obtain a device record, look up logistics delivery ranges, and run a zero-value credit card authorization to validate a payment method before an order proceeds. ## For AI agents Register and validate retail customers, validate a vehicle plate, create and finalize orders, track order status, look up logistics ranges, and run a card validation. ## Scope Does not handle marketing, inventory forecasting, or customer support. Use for registering customers and placing, finalizing, and tracking retail orders only. ## Capabilities - Register a retail customer and validate their details - Validate a vehicle plate before an order - Create a retail order and finalize it - Check the status of a placed order - Look up logistics delivery ranges for an order - Run a zero-value authorization to validate a credit card ## Use cases ### Agent-driven retail order placement An AI agent connected through Jentic takes a retail order from start to finish: it validates the customer, creates the order, and finalizes it, then checks the status to confirm it went through. Because the agent discovers operations by intent, the full order flow runs without a developer wiring each ordering endpoint by hand. Example prompt: Validate a customer, create a retail order for them, finalize it, and then check the order status ### Customer and payment validation Before an order proceeds the API validates the pieces that must be correct: it validates the customer and vehicle plate and runs a zero-value authorization against the credit card. An agent can run these checks up front so that only valid customers and payment methods reach the order step, cutting failed orders downstream. Example prompt: Validate a customer and their vehicle plate, then run a zero-value authorization to confirm the card is usable ### Logistics range lookup The logistics endpoint returns the delivery ranges available for an order, so an agent can confirm what is serviceable before finalizing. This lets an ordering assistant set accurate delivery expectations grounded in the API's logistics data rather than assuming coverage. Example prompt: Look up the logistics delivery ranges and confirm whether a destination is serviceable before finalizing the order ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/varejo/v1/cliente/cadastrar` | Register a customer | | POST | `/varejo/v1/cliente/validar` | Validate a customer | | POST | `/varejo/v1/pedido/cadastrar` | Create a retail order | | POST | `/varejo/v1/pedido/finalizar` | Finalize an order | | POST | `/ura-pedido/v1/pedido/status` | Check order status | | GET | `/order/logistics/ranges` | Look up logistics delivery ranges | | POST | `/validacao/v2/pagamento/auth-zero` | Validate a credit card with a zero-value authorization | ## Key resources - **Cliente** — Register and validate retail customers - **Pedido** — Create, finalize, and check the status of retail orders - **Logistics** — Look up delivery ranges for an order - **Pagamento** — Run a zero-value authorization to validate a credit card - **Dispositivo** — Obtain a device record used by the ordering flow ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 42 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 87 / 100 - Developer Experience & Jentic Compatibility: 55 / 100 - AI-Readiness & Agent Experience: 20 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 50 / 100 - **View full report:** https://jentic.com/apis/apisemparar.com.br/apisemparar/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Sem Parar Retail Orders API by hand means handling its x-api-key auth, sequencing customer validation before order creation, and pointing at the right staging or production host. Through Jentic you install once, import the API from the Directory, store the key once, and your agent calls it. - **Permission scoping:** The Sem Parar Retail Orders API carries its targets in the request body, so rules bound which operations your agent may call: you can allow customer validation and order-status reads while leaving order creation and finalization out unless you add them. You choose the operations it may use. - **Credential handling:** Your Sem Parar API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a retail order' or 'check order status', and Jentic returns the matching Sem Parar operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Shopify** — Shopify manages orders, products, and checkout for a full online storefront - **BigCommerce Orders** — BigCommerce's orders API creates and manages orders within a hosted commerce platform - **Stripe** — Stripe processes the actual card payment that a validated order needs to collect ## FAQ ### What authentication does the Sem Parar Retail Orders API use? The Sem Parar Retail Orders API authenticates with an API key sent in the x-api-key request header, as declared in its OpenAPI spec. Through Jentic the key is stored once by your own self-hosted instance and injected at call time, so it never appears in the agent's prompt or logs. ### Can I place and track orders with the Sem Parar Retail Orders API? Yes. You register and validate a customer, create a retail order, finalize it, and then check its status. Logistics and card-validation operations let you confirm delivery coverage and payment before the order proceeds. ### Is there a Sem Parar Retail Orders API MCP server? You do not need an MCP server to give your agent the Sem Parar Retail Orders API. Jentic connects it directly from the API Directory: import the API, store your API key once, and your agent places and tracks orders on demand without loading another server's tool definitions into its context. ### Can I limit what my agent is allowed to do with the Sem Parar Retail Orders API? Yes. Write a rule that allows only the customer-validation and order-status read operations, so the agent can check customers and track orders but cannot create or finalize orders unless you add those, and every call it makes is logged for review. Sem Parar carries its targets in the request body, so rules bound which operations the agent may call. ### What are the rate limits for the Sem Parar Retail Orders API? The OpenAPI spec does not specify rate limits for the Sem Parar Retail Orders API. Check the vendor documentation for current limits before driving high order volume, and note the spec exposes separate staging and production hosts. ### How do I place an order with the Sem Parar Retail Orders API through Jentic? Search Jentic for an intent such as 'create a retail order', and it returns the matching operation with its input schema so your agent submits the customer and order details correctly. To run it on your own infrastructure, install Jentic One from its GitHub repo.