For Agents
Scan a UK traffic or parking notice, get the grounds and a drafted appeal, and file it with the issuing authority. Authenticates with a bearer key for the notice workflow; status, guides, codes, and deadline lookups are public.
Use for: Scan a parking ticket and tell me whether it is worth appealing, File an appeal for this PCN, Check the deadline to appeal a ULEZ notice, Explain what a contravention code means
Not supported: Does not pay the original fine, provide court representation, or handle non-UK traffic penalties. Use for checking, drafting, and filing appeals against UK parking and traffic notices only.
The AppealGo API scans a UK parking ticket, council PCN, private parking charge, bus lane, ULEZ, or Clean Air Zone notice, returns the grounds for an appeal with a drafted response, and files that appeal with the issuing authority. Checking a notice is free; filing is charged per notice or covered by a plan. Alongside the notice workflow it exposes free public lookups: a status check by customer reference, searchable appeal guides served as Markdown, contravention code explanations, and a statutory deadline calculator.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AppealGo 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%2Fappealgo.com%2Fappealgo" | 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%2Fappealgo.com%2Fappealgo" | 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 AppealGo API.
Scan a UK parking ticket, PCN, bus lane, ULEZ, or Clean Air Zone notice to get the grounds for appeal
File a drafted appeal against a notice with the issuing authority
Calculate the statutory appeal deadlines for a notice
Look up and explain a contravention code
Search the appeal guides and read them as Markdown
Check an appeal's status by customer reference
Patterns agents use AppealGo API for, with concrete tasks.
★ Agent-Assisted Parking Appeal
An AI agent connected through Jentic scans a photographed parking or traffic notice, reads back the grounds AppealGo found and the drafted appeal, and files it with the issuing authority once a person approves. Because checking is free and filing is a separate paid step, the agent can assess a ticket's merits before anything is submitted.
Scan this parking notice, summarise the grounds for appeal, and file the appeal only if the grounds are strong
Deadline and Grounds Triage
A workflow scans each incoming notice and calculates its statutory appeal deadline so an operator sees which tickets must be answered first and which have the strongest grounds. The deadline calculator and the scan grounds together turn a pile of notices into a prioritised queue.
For each notice, return its appeal deadline and the grounds found, sorted by the soonest deadline
Contravention Code Lookup
A support tool resolves a contravention code into a plain explanation and pulls the relevant appeal guide so a user understands what they were charged for and how to contest it. The code explanations and Markdown guides make the lookup self-contained for an answer engine or chatbot.
Explain the contravention code on this notice and return the matching appeal guide
13 endpoints — the appealgo api scans a uk parking ticket, council pcn, private parking charge, bus lane, ulez, or clean air zone notice, returns the grounds for an appeal with a drafted response, and files that appeal with the issuing authority.
METHOD
PATH
DESCRIPTION
/notices
List this account's notices
/notices
Scan a notice
/notices/{id}/file
File the appeal
/codes
List or search contravention codes
/deadlines
Calculate statutory deadlines for a notice
/guides
Search the appeal guides
/notices
List this account's notices
/notices
Scan a notice
/notices/{id}/file
File the appeal
/codes
List or search contravention codes
/deadlines
Calculate statutory deadlines for a notice
/guides
Search the appeal guides
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 AppealGo API by hand means creating and carrying a bearer key, separating the free public lookups from the authenticated scan-and-file calls, and respecting the per-key scan budget. Through Jentic you install once, import AppealGo from the API Directory, store the key once, and your agent calls it.
Permission scoping
AppealGo puts the notice id in the URL path, so a rule can let your agent scan and check notices while leaving the file-the-appeal operation out, or pin it to acting on one notice. You choose the operations it may call, so filing an appeal is not included unless you add it.
Credential isolation
Your AppealGo key 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 'scan a parking ticket' or 'check an appeal deadline', and Jentic returns the matching AppealGo operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using AppealGo API through Jentic.
Is there an AppealGo MCP server?
Yes. AppealGo offers an MCP server that exposes the same operations. You can also connect it directly through Jentic: your agent gets the full 13-endpoint surface without loading another server's tool definitions into its context, your key is injected at call time by your self-hosted instance instead of living in a config file, and your rules decide which operations the agent may call.
Can I limit what my agent is allowed to do with the AppealGo API?
Yes. Write a rule that allows scanning a notice and reading its status and deadlines but not the file-the-appeal operation, so the agent can assess a ticket without ever submitting an appeal on your behalf, and every call it makes is logged. Because the notice id is in the URL path, you can also bound the agent to one notice.
What authentication does the AppealGo API use?
The AppealGo API authenticates with a bearer token, an ag_live_ key you create in your profile, per its OpenAPI spec. The public status, guide, contravention-code, and deadline lookups need no key. Through Jentic the key is stored encrypted by your own instance and added at call time, so it never appears in the agent's prompt or logs.
Can I check whether a parking ticket is worth appealing with the AppealGo API?
Yes. Scanning a notice returns the grounds AppealGo found plus a drafted appeal, and the deadline endpoint returns the statutory dates for that notice, so an agent can judge both the merits and the timing before anything is filed. Checking a notice is free, and only the filing step is charged.
What are the rate limits for the AppealGo API?
Each API key may run 25 scans per day according to the API's own description; the spec does not publish limits for the free lookup endpoints. For current limits and plan allowances, see the AppealGo documentation at https://appealgo.com.
How do I file a parking appeal with the AppealGo API through Jentic?
Import the AppealGo API from the Jentic API Directory, then have your agent issue a request such as 'scan this parking ticket and file an appeal if there are grounds'. Jentic matches the intent to the scan and file operations and returns their input schemas so the agent builds the right calls, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED