For Agents
Programmatically execute graphql query. Covers 1 operations with bearer authentication.
Use for: I need to execute graphql query, Find available e commerce operations, Get the current status of Whatnot Seller API resources, List all records from Whatnot Seller API
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
The Whatnot Seller API is a GraphQL API for managing products and receiving notifications when items sell on the Whatnot marketplace. Note: This is a GraphQL API accessed via a single POST endpoint. The API exposes 1 endpoints secured with bearer authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Whatnot Seller API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fwhatnot.com%2Fwhatnot" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fwhatnot.com%2Fwhatnot" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Whatnot Seller API.
Execute GraphQL query
Manage e commerce data programmatically
Integrate Whatnot Seller API into automated workflows
Query and filter Whatnot Seller API records by parameters
Monitor Whatnot Seller API operational status and events
Patterns agents use Whatnot Seller API for, with concrete tasks.
★ E-Commerce Operations
Use the Whatnot Seller API to perform e commerce operations programmatically. The API provides 1 endpoints covering core functionality including execute graphql query.
Call POST /seller-api/graphql to execute graphql query
Data Retrieval and Monitoring
Query Whatnot Seller API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary Whatnot Seller API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Whatnot Seller API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'execute graphql query', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — the whatnot seller api is a graphql api for managing products and receiving notifications when items sell on the whatnot marketplace.
METHOD
PATH
DESCRIPTION
/seller-api/graphql
Execute GraphQL query
/seller-api/graphql
Execute GraphQL query
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Whatnot Seller API by hand means placing its bearer token on the single GraphQL endpoint and handling retries yourself. Through Jentic you install once, import the Whatnot Seller API from the API Directory, store the token once, and your agent calls it.
Permission scoping
The Whatnot Seller API exposes one GraphQL operation and carries the query in the request body rather than in the path, so limit the agent to that operation. You choose the operations it may call, so nothing beyond the GraphQL endpoint runs unless you add it.
Credential isolation
Your Whatnot Seller API token 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.
Intent-based discovery
Agents search Jentic by intent such as 'run a seller GraphQL query', and Jentic returns the matching Whatnot Seller API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
Specific to using Whatnot Seller API through Jentic.
What authentication does the Whatnot Seller API use?
The Whatnot Seller API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I execute graphql query with the Whatnot Seller API?
Yes. Use the POST /seller-api/graphql endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Whatnot Seller API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I execute graphql query through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'execute graphql query'. Jentic returns the matching Whatnot Seller API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Whatnot Seller API have?
The Whatnot Seller API exposes 1 endpoints covering graphql operations.
Can I limit what my agent is allowed to do with the Whatnot Seller API?
Yes. Jentic One is self-hosted by you, so your own rules decide which operations and credentials the agent may use. The Whatnot Seller API exposes a single GraphQL operation at POST /seller-api/graphql, and you choose whether the agent may call it, so nothing beyond that endpoint runs unless you add it. Your bearer token stays with your instance and is injected only when the agent runs the operations you permit.
GET STARTED