Jensmostaert3 API of the Adshot Core service
Browse all Swaggerhub Jensmostaert3 APIsCommunity OpenAPI document · agent-readyDeveloper ToolsSource Controlnone34 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically list / search all gamers., retrieve details of a specific gamer.. Covers 34 operations.
Use for: I need to / search all gamers., I want to details of a specific gamer., Search for gamer profile., Find all the gamer resource owned by the authenticated user.
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
This is the API definition for the Adshot Core service. The API exposes 34 endpoints.
Install Jentic One Beta
Connect the API of the Adshot Core service to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API of the Adshot Core service, 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.
1
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%2Fswaggerhub.jensmostaert3%2Fapi-of-the-adshot-core-service" | sh2
Step 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%2Fswaggerhub.jensmostaert3%2Fapi-of-the-adshot-core-service" | 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.
Capabilities
What an agent can do with API of the Adshot Core service API.
List / search all Gamers.
Retrieve details of a specific Gamer.
Update Gamer profile.
Query and filter API of the Adshot Core service records by parameters
Monitor API of the Adshot Core service operational status and events
Use Cases
Patterns agents use API of the Adshot Core service API for, with concrete tasks.
★ Developer Tools Operations
Use the API of the Adshot Core service to perform developer tools operations programmatically. The API provides 34 endpoints covering core functionality including list / search all gamers., retrieve details of a specific gamer., update gamer profile..
Call GET /v1/gamers to list / search all gamers.
Automated Operations on Gamers Management
Automate operations on gamers operations by combining multiple API of the Adshot Core service endpoints. Agents can retrieve details of a specific gamer. and then update gamer profile. in a single workflow.
Call GET /v1/gamers/{id} to retrieve details of a specific gamer., then verify the result
AI Agent Integration via Jentic
AI agents discover and call API of the Adshot Core service 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 none tokens manually.
Search Jentic for 'list / search all gamers.', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
34 endpoints — this is the api definition for the adshot core service.
METHOD
PATH
DESCRIPTION
GET
/v1/gamers
List / search all Gamers.
GET
/v1/gamers/{id}
Retrieve details of a specific Gamer.
PATCH
/v1/gamers/{id}
Update Gamer profile.
GET
/v1/gamer
Retrieve the Gamer resource owned by the authenticated user.
PATCH
/v1/gamer
Update Gamer profile owned by the authenticated user.
GET
/v1/advertisers
List / search through all Advertiser profiles
GET
/v1/advertisers/{id}
Retrieve details of a specific Advertiser
PATCH
/v1/advertisers/{id}
Update a specific Advertiser
GET
/v1/gamers
List / search all Gamers.
GET
/v1/gamers/{id}
Retrieve details of a specific Gamer.
PATCH
/v1/gamers/{id}
Update Gamer profile.
GET
/v1/gamer
Retrieve the Gamer resource owned by the authenticated user.
PATCH
/v1/gamer
Update Gamer profile owned by the authenticated user.
GET
/v1/advertisers
List / search through all Advertiser profiles
GET
/v1/advertisers/{id}
Retrieve details of a specific Advertiser
PATCH
/v1/advertisers/{id}
Update a specific Advertiser
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Adshot Core service by hand means reading its spec, building calls across its gamers and advertisers endpoints, and handling request formatting and retries yourself. Through Jentic you install once, import Adshot Core from the API Directory, store any required connection detail once, and your agent calls it.
Permission scoping
Adshot Core puts the gamer and advertiser ids in the URL path (/v1/gamers/{id}, /v1/advertisers/{id}), so a rule can pin your agent to reading one gamer or one advertiser. You choose the operations it may call, so the PATCH update operations are not included unless you add them.
Credential isolation
Any connection detail the Adshot Core service needs 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 'list or search all gamers', and Jentic returns the matching Adshot Core operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using API of the Adshot Core service API through Jentic.
What authentication does the API of the Adshot Core service use?
The API of the Adshot Core service uses no authentication. 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 list / search all gamers. with the API of the Adshot Core service ?
Yes. Use the GET /v1/gamers endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the API of the Adshot Core service ?
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 list / search all gamers. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list / search all gamers.'. Jentic returns the matching API of the Adshot Core service operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the API of the Adshot Core service have?
The API of the Adshot Core service exposes 34 endpoints covering operations on gamers, operations on advertisers, operations on campaigns operations.
Can I limit what my agent is allowed to do with the Adshot Core API?
Yes. Because you run Jentic One yourself, your own rules decide which Adshot Core operations and credentials your agent can use. Adshot Core puts the gamer and advertiser ids in the URL path (/v1/gamers/{id} and /v1/advertisers/{id}), so a rule can pin your agent to reading a single gamer or advertiser. You choose the operations it may call, so the PATCH update operations stay excluded unless you add them.
GET STARTED