Revibe
Revibe (Revibe Technology FZ-LLC) is a UAE-based e-commerce marketplace for certified refurbished and renewed electronics — iPhones, Samsung phones, MacBooks, laptops, iPads, TVs, and accessories — sold with a 12-month warranty, a 10-day return window, free UAE delivery, and buy-now-pay-later options (Tabby, Tamara, Split). Every device passes a 50-point quality check and the company reports accepting only one in four supplier lots. Revibe operates in the UAE (revibe.me), Saudi Arabia (sa.revibe.me), and South Africa (revibe.co.za), and runs a trade-in program (sell.revibe.me). The storefront is built on Shopify and natively implements the Universal Commerce Protocol (UCP, ucp.dev), exposing a hosted MCP endpoint for agent-driven catalog search, cart, and human-approved checkout, plus a published /llms.txt and Shopify Customer Account OpenID Connect discovery. Backed by Partech.
Revibe publishes 1 API on the APIs.io network. Tagged areas include Company, Marketplace, E-Commerce, Refurbished Electronics, and Consumer Electronics.
Revibe’s developer surface includes engineering blog, signup flow, authentication, and 8 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Revibe UCP Shopping (MCP)
Agent-driven commerce surface for the Revibe Shopify store implemented via the Universal Commerce Protocol (UCP). A hosted MCP endpoint exposes catalog search, cart, checkout, a...
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
revibe-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API