Official vendor OpenAPI document · agent-readySecurityThreat Detectionnone declared in the spec; paid routes take an x402 USDC payment or a prepaid key sent as the X-API-Key header40 EndpointsREST
For Agents
Check a Solana pump.fun or Robinhood Chain token for rug-pull risk before a trade, poll new launches with calibrated rug and graduation odds, and look up a creator's launch history. Free routes need no payment; paid routes use x402 or a prepaid X-API-Key.
Use for: Check whether this pump.fun token is likely to rug before I buy, I want a quick free risk verdict on a Solana mint, Poll new pump.fun launches with high graduation odds, Get the creator's launch and rug history for this wallet
Not supported: Does not execute trades, hold wallets, or guarantee token safety, and does not cover established exchange-listed coins. Use for rug-risk checks and launch data on pump.fun and Robinhood Chain tokens only.
The loophole tape API checks new pump.fun memecoins on Solana and Robinhood Chain pons tokens for rug-pull risk, returning calibrated rug and graduation probabilities, holder concentration, creator records, and observed rug flags computed from its own capture of on-chain events. Free routes cover a live radar of new launches, a coarse pre-trade token check, three-item delayed samples, label definitions, and the calibration tables behind the probabilities. Paid routes are priced per request in USDC on Solana or Base through x402 with no account, from $0.001 to $0.04 per data call and $5.00 per daily dataset file, and a prepaid key bought once can be sent as the X-API-Key header instead. Responses report coverage, freshness, and the numeric evidence behind each flag.
Install Jentic One Beta
Connect the loophole tape to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the loophole tape, 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%2Floopholetape.com%2Floopholetape" | 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%2Floopholetape.com%2Floopholetape" | 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 loophole tape API.
Get a verdict word (avoid, caution, or no_flags_observed) with one reason for any Solana or pons token through the free GET /v1/token_check/{mint}
Fetch the paid compact rug check for one pump.fun mint with calibrated P(rug within 5 min), P(true graduation), and observed flags via GET /v1/check/mint/{mint}
Poll newly launched pump.fun tokens with their odds through GET /v1/launches/since, up to 100 per call
Screen up to 25 caller-selected pump.fun mints in one payment with GET /v1/check/batch
Judge a launch by its creator's earlier pump.fun record, including n_launches, graduations, and rugs, via GET /v1/creator/{address}
List recent rug and close flags by mechanism, such as creator_sold, bundle_dumped, and curve_drained, through GET /v1/rugs/recent
Download one UTC day of pump.fun launches with outcome labels as parquet for backtesting via GET /v1/datasets/pumpfun_launches/{day}
Use Cases
Patterns agents use loophole tape API for, with concrete tasks.
★ Pre-trade rug check by a trading agent through Jentic
A trading agent checks a token before a swap by searching Jentic for 'check a Solana token for rug risk' and receiving the loophole tape operation with its input schema. It calls the free GET /v1/token_check/{mint} for a coarse verdict, and when the verdict is caution it can pay for GET /v1/check/mint/{mint} to read the calibrated P(rug within 5 min), observed flags, and their first-observed times before deciding.
Call GET /v1/token_check/{mint} for the mint the user pasted, report the verdict word and reason, and if the verdict is caution call GET /v1/check/mint/{mint} and summarise the observed flags
New-launch screening bot
A bot polls GET /v1/launches/since with the last unix timestamp it saw, receiving up to 100 new covered pump.fun launches per call, oldest first, each with creator, reserve, buyer inflow, top-5 holder share, and calibrated odds. Filtering on min_p_grad and no_avoid narrows the feed to launches with graduation potential and no avoid verdict.
Call GET /v1/launches/since with since set to the last poll time and min_p_grad 0.3, then list the name, symbol, and graduation probability of each returned launch
Creator due diligence
Before backing a new memecoin, look at what its creator launched before. GET /v1/creator/{address} returns stats over every launch loophole tape has seen from that wallet, counting only outcomes known at request time: launches, resolved launches, graduations, and rugs by drain or dev dump, so a repeat rugger stands out.
Call GET /v1/creator/{address} for the creator wallet of a new launch and report how many earlier launches graduated and how many rugged
Rug model backtesting
Researchers building a rug or graduation model download full UTC days of pump.fun launches as parquet. GET /v1/datasets lists available days with sizes and sha256 hashes, and GET /v1/datasets/pumpfun_launches/{day} returns every launch the capture saw that day with creator, dev buy, and outcome labels such as rug delay and migration delay.
Call GET /v1/datasets to find the most recent available day, then download it with GET /v1/datasets/pumpfun_launches/{day} and verify the sha256 hash
Key Endpoints
40 endpoints — the loophole tape api checks new pump.
METHOD
PATH
DESCRIPTION
GET
/v1/token_check/{mint}
Free coarse rug-risk verdict for one token
GET
/v1/check/mint/{mint}
Paid compact rug check for one pump.fun mint
GET
/v1/verdict/{mint}
Rug pull risk verdict with reason and share_url
GET
/v1/launches/since
Poll new pump.fun launches with odds
GET
/v1/radar
Free radar of new mints ranked by rug and graduation odds
GET
/v1/creator/{address}
Creator launch, graduation, and rug record
GET
/v1/rugs/recent
Recent rug and close flags by mechanism
GET
/v1/rhc/curve/{address}
Robinhood Chain token verdict, holders, and tax
GET
/v1/token_check/{mint}
Free coarse rug-risk verdict for one token
GET
/v1/check/mint/{mint}
Paid compact rug check for one pump.fun mint
GET
/v1/verdict/{mint}
Rug pull risk verdict with reason and share_url
GET
/v1/launches/since
Poll new pump.fun launches with odds
GET
/v1/radar
Free radar of new mints ranked by rug and graduation odds
GET
/v1/creator/{address}
Creator launch, graduation, and rug record
GET
/v1/rugs/recent
Recent rug and close flags by mechanism
GET
/v1/rhc/curve/{address}
Robinhood Chain token verdict, holders, and tax
Jentic AI Readiness Score
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.
L
loophole tape
- Foundational (C+)57/100
82
Foundational Compliance43
Developer Experience & Jentic Compatibility37
AI-Readiness & Agent Experience94
Agent Usability100
Security71
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
82
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
96%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
30%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
43
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: D-Signals: 4
2%
Example Density
How richly the API is illustrated with examples.
24%
Example Validity
Percentage of examples that conform to their schemas.
44%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
37
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
37%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
72%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
38%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
71
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
71%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring loophole tape by hand means telling free routes from paid ones, handling HTTP 402 payment challenges through x402 or a prepaid X-API-Key header, and respecting the 429 cap on the free token check. Through Jentic you install once, import loophole tape from the API Directory, add your prepaid key if you use one, and your agent calls it.
Permission scoping
Rules filter by method and path, so you can keep the agent on free routes such as the radar and the coarse token check and leave paid checks, dataset downloads, key purchases, and alert subscriptions out. Mint addresses sit in the path (/v1/check/mint/{mint}), so a rule can also pin paid checks to one token.
Credential isolation
If you use a prepaid loophole tape key, it is kept encrypted by your own Jentic One instance and attached as the X-API-Key header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'check a Solana token for rug risk' or 'poll new pump.fun launches', and Jentic returns the matching loophole tape operation with its input schema, including parameters like mint, since, and min_p_grad, so the agent calls the right route without reading the route index.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using loophole tape API through Jentic.
How do I pay for or authenticate to the loophole tape API?
The OpenAPI spec declares no security scheme. Free routes such as GET /v1/radar and GET /v1/token_check/{mint} need no payment or key. Paid routes return HTTP 402 and are paid per request in USDC on Solana or Base through x402, or by sending a prepaid lt_ key, bought through GET /v1/keys/new or GET /v1/keys/trial, as the X-API-Key header. Through Jentic, a prepaid key is kept encrypted by your own Jentic One instance and attached at execution time.
Can I check a token for rug risk for free with the loophole tape API?
Yes. GET /v1/token_check/{mint} takes a pump.fun mint, any other Solana mint, a Robinhood Chain pons address, or a pasted token link, and returns a verdict word (avoid, caution, or no_flags_observed), one reason, coverage, and age. A no_flags_observed verdict is not a safety guarantee; for calibrated odds and evidence use the paid GET /v1/check/mint/{mint}.
What are the rate limits for the loophole tape API?
The OpenAPI spec states that the free GET /v1/token_check/{mint} allows 30 calls an hour per caller by default, returning HTTP 429 over it, plus a daily cap across all callers. Limits for paid routes are not listed in the spec; see https://api.loopholetape.com for current details.
How do I poll new pump.fun launches with loophole tape through Jentic?
Install Jentic One, add the loophole tape API from the Jentic directory, and have your agent search for 'poll new pump.fun launches'. Jentic returns GET /v1/launches/since with its since, limit, no_avoid, and min_p_grad parameters, and the agent calls it with the last timestamp it saw. To run it on your own infrastructure, install Jentic One from its GitHub repo.
What does the loophole tape API cost?
Per the spec, paid data calls cost from $0.001 to $0.04 each through x402, and a daily dataset file costs $5.00. Prepaid keys come as a $0.10 trial worth about twenty rug checks or a $2.00 key; credit does not expire, and GET /v1/keys/balance shows the remaining balance for free.
Is there a loophole tape MCP server?
You don't need an MCP server to give your agent loophole tape. Jentic connects the REST API directly from the API Directory: import it and your agent finds the operations it needs by intent, without loading extra tool definitions into its context.
Can I limit what my agent is allowed to do with the loophole tape API?
Yes. A rule allowing only GET /v1/token_check/{mint} and GET /v1/radar keeps the agent on free routes, so it cannot spend prepaid credit. Add GET /v1/check/mint/{mint} when you want paid checks, and the agent's calls are logged for review.
GET STARTED