canonical: https://jentic.com/apis/epdk.gov.tr/epdk # EPDK Charging Network Operator License Query The EPDK Charging Network Operator License Query API checks electric-vehicle charging network operator licenses issued by Turkey's Energy Market Regulatory Authority. Its single lookup operation accepts a license number, a company title, a tax number, or a license-status filter and returns the matching operator license records. It is a read-only public reference service for confirming that a charging network operator holds a valid license. ## For AI agents Look up EV charging network operator licenses from Turkey's EPDK by license number, company title, tax number, or license status. ## Scope Does not issue licenses, process applications, or handle charging payments. Use for querying EPDK charging network operator license records only. ## Capabilities - Look up a charging network operator license by its license number - Search for an operator license by company title or tax number - Filter operator license records by license status ## Use cases ### Agent-Driven License Verification An AI agent connected through Jentic confirms that an EV charging network operator is licensed by querying the EPDK register with a license number or tax number and reading back the matching record. Because the service is a single read-only lookup, the agent resolves a compliance question with one bounded call rather than scraping a regulator portal. Example prompt: Query the EPDK register by a given license number and return the operator's title and license status ### Operator Compliance Screening A compliance workflow screens charging network operators before onboarding them. The EPDK lookup accepts a company title or tax number and returns the operator's license records, so an agent verifies a counterparty's licensed status against the official regulator source. Example prompt: Look up an operator by tax number and flag it if no valid license record is returned ### Licensed Operator Discovery A market-research task builds a list of licensed charging network operators by filtering the register on license status. The EPDK API returns the operator records matching a status filter, letting an agent assemble a current view of licensed operators from the authoritative source. Example prompt: Filter the register by active license status and compile the licensed operators returned ## Key resources - **Operator licenses** — Query charging network operator license records by number, title, tax number, or status ## 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:** 0 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 74 / 100 - Developer Experience & Jentic Compatibility: 44 / 100 - AI-Readiness & Agent Experience: 31 / 100 - Agent Usability: 94 / 100 - Security: 100 / 100 - AI Discoverability: 0 / 100 - **View full report:** https://jentic.com/apis/epdk.gov.tr/epdk/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:** The EPDK license query is a single public endpoint, so wiring it by hand still means formatting the request and parsing the response. Through Jentic you import it from the API Directory and your agent calls it, with no key to manage because the endpoint needs no credential. - **Permission scoping:** The API exposes one read-only lookup operation, so a rule limits your agent to that single query and nothing else. There are no write or delete operations to expose, and the agent can only read license records. - **Credential handling:** The EPDK license query needs no API key, so your agent holds no secret for it. For the authenticated APIs in your directory, your own Jentic One instance keeps each key encrypted and injects it at execution time, so it never reaches the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'look up a charging operator license', and Jentic returns the EPDK lookup operation with its input schema so the agent queries the register with the right fields. ## Related APIs - **UK Companies House API** — Another official register lookup, covering UK company records rather than Turkish charging-operator licenses. - **Tesla Fleet API** — Vehicle and charging data that complements the licensing lookup when working across the EV charging ecosystem. ## FAQ ### What authentication does the EPDK license query API use? The EPDK charging network license query requires no authentication: its OpenAPI spec declares no security scheme, so the single lookup operation is public. Through Jentic you import it from the API Directory and your agent calls it like any other operation, with no key to manage. ### Can I check an EV charging operator's license with the EPDK API? Yes. The lookup accepts a license number, a company title, a tax number, or a license-status filter and returns the matching operator license records from Turkey's Energy Market Regulatory Authority. Your agent reads back whether an operator holds a valid license. ### Is there an EPDK MCP server? You do not need an MCP server to give your agent the EPDK license query. Jentic connects it directly from the API Directory: import it and your agent calls the single lookup operation on demand without loading an extra server's tool definitions into its context. ### Can I limit what my agent is allowed to do with the EPDK license query API? Yes, though the surface is already minimal: a rule can allow the one read-only lookup operation and nothing else. Since the API has no write operations and needs no credential, the agent can only read license records, and every call it makes is logged. ### How do I verify a charging operator license through Jentic? Install the Jentic One command line with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the EPDK license query from the Jentic directory and search by intent such as 'look up a charging operator license'. Jentic returns the lookup operation with its input schema so your agent builds a valid query. To run it on your own infrastructure, install Jentic One from its GitHub repo.