Built for Your Job

    What Are You Trying to Do?

    One data layer, built for whatever job you need it to do, from tracking one marketplace to building your own AI shopping agent. Pick your use case below.

    Get API KeyView Pricing

    Source-Specific Tracking

    03

    Amazon Price Tracking

    Buy Box, offers, and seller data across 22 Amazon marketplaces.

    Explore

    Google Shopping Price Tracking

    GTIN-matched merchant listings, not keyword-guessed.

    Explore

    Catch Buy Box Losses

    Live Buy Box ownership and offer-stack monitoring for Amazon sellers.

    Explore

    Cross-Source Monitoring

    03

    Monitor Competitor Prices

    Buy-box owners, promos and stock status, signals for your repricer or BI stack.

    Explore

    Power Dynamic Repricing

    Feed automated repricing logic with validated, real-time data.

    Explore

    MAP Monitoring

    Feed seller, offer and price observations into your own MAP and brand-protection workflow.

    Explore

    General & Emerging

    02

    Track Prices Across Any Source

    The general-purpose entry point, 12 marketplaces, one endpoint.

    Explore

    AI Shopping Agents

    The data layer for building accurate AI shopping agents.

    Built on GTIN-native matching, the accuracy an AI agent needs to trust a price.

    Explore

    Shared Foundation

    Different Jobs, One Data Layer

    Every use case on this page reads from the same infrastructure. Start with one job, add the next without changing your integration.

    One Key

    A single credential covers every use case on this page, no per-source onboarding.

    One Schema

    The same normalized JSON contract, whichever marketplace the request resolves against.

    Twelve Sources

    Amazon, Google Shopping, ebay, Otto, Kaufland and more, behind one endpoint.

    Not Sure Which Fits?

    Talk to us

    Support

    Before You Pick a Use Case

    The questions teams ask whichever job they start with. Full answers live in the knowledgebase.

    Browse all FAQs

    No. kwery is the data layer underneath whatever pricing logic you already run. Your ERP, PIM, repricer, or custom engine keeps full control. We only deliver the marketplace data they consume.

    The first successful call typically takes minutes using the copy-paste examples in the docs. Teams going to production usually spend a few days wiring webhook delivery, retries and their own storage around it. API documentation.

    Twelve sources today: Amazon, Google Shopping, ebay, Idealo, Kaufland, Otto, billiger.de, guenstiger.de, Walmart, Lidl, AliExpress, and Rakuten. Each one has its own page in the Source Library with the identifiers it accepts and the countries it covers. View Source Library.

    Yes. You specify which sources a job should cover, and results come back per source in the same response schema, so comparing an Amazon observation with an Idealo one needs no source-specific handling.

    Plans are scoped by sources, request volume, and delivery model (pull, webhook, stream). Self-serve tiers have published per-credit pricing; Direct API plans are sized to your real usage during onboarding. Pricing overview.

    Find Your Use Case, Then Ship It

    Every job on this page runs on the same normalized pricing data layer, one key, one schema, twelve sources.

    Get API KeyView Documentation
    Free Tier Available
    Enterprise SLA
    Global Scale