Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the The Stall, 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%2Fintuitek.ai%2Fintuitek" | 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%2Fintuitek.ai%2Fintuitek" | 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 The Stall API.
Pull SEC EDGAR due diligence for a US public company by ticker, including CIK, SIC code, and filing history
Run an entity clearance check on a business name and website before an agent acts on it
Read stock fundamentals and Wall Street analyst ratings and price targets for a ticker
Look up domain WHOIS/RDAP registration data and DNS records for a domain
GET STARTED
Score an email address for deliverability with a DELIVERABLE, RISKY, UNDELIVERABLE, or INVALID verdict
Search NVD CVE records by CVE ID, keyword, or severity
Buy prepaid call credits by card and retrieve the bearer token after checkout
Patterns agents use The Stall API for, with concrete tasks.
★ AI research agent paying per call for company data
A developer's agent connected through Jentic searches by intent, finds the matching Stall capability such as company intel or equity fundamentals, and calls it with a prepaid bearer token injected at execution time. The agent gets SEC EDGAR and market data for a ticker without signing up to separate data vendors, and the token never enters its context.
Call GET /cap/company-intel with ticker 'AAPL' and GET /cap/equity-fundamentals with the same ticker, then summarise CIK, SIC description, P/E, and market cap
Counterparty clearance before an agent acts
Before an agent emails, pays, or signs up with a business it found online, it needs a basic legitimacy check. The entity clearance capability takes a required name and website plus an optional email and intended_action, probes the live site, checks domain and contact consistency, and returns graded evidence, risk flags, a recommended_action, and a sha256 receipt.
Call GET /cap/entity-clearance with name 'Acme Tools Ltd', website 'https://acmetools.example', and intended_action 'purchase', then stop if recommended_action is not to proceed
Lead and domain hygiene
Sales and ops tools clean inbound leads by checking the email and the company domain. The email verification capability checks RFC-5322 syntax, disposable domains, and MX records and returns a 0-100 score with a verdict, while domain WHOIS returns registration and expiry dates, registrar, and nameservers.
Call GET /cap/email-verify for 'jane@example.org' and GET /cap/domain-whois for 'example.org', then flag the lead if the verdict is RISKY or the domain was registered recently
Vulnerability lookups for a dependency
A coding agent reviewing dependencies can query NVD records through the CVE capability by CVE ID, keyword, or severity, with days and limit filters. Results carry CVSS score, attack vector, CWEs, and references, so the agent can decide whether a version bump is urgent.
Call GET /cap/cve-intel with query 'openssl', severity 'CRITICAL', and days 30, then list the CVE IDs with their CVSS scores
312 endpoints — the stall api from intuitek serves 301 pay-per-call data capabilities under /cap/ paths, covering sec edgar company profiles and filings, us equity fundamentals and analyst ratings, crypto and defi market data, domain whois and dns lookups, email verification, cve lookups, and ai image generation.
METHOD
PATH
DESCRIPTION
/catalog
List all capabilities with prices and schemas
/cap/company-intel
SEC EDGAR company profile by ticker
/cap/entity-clearance
Business legitimacy clearance check
/cap/equity-fundamentals
Stock valuation fundamentals
/cap/email-verify
Email deliverability score
/cap/domain-whois
Domain WHOIS/RDAP lookup
/v1/fiat/checkout
Buy prepaid credits by card
/v1/fiat/token
Retrieve bearer token after payment
/catalog
List all capabilities with prices and schemas
/cap/company-intel
SEC EDGAR company profile by ticker
/cap/entity-clearance
Business legitimacy clearance check
/cap/equity-fundamentals
Stock valuation fundamentals
/cap/email-verify
Email deliverability score
/cap/domain-whois
Domain WHOIS/RDAP lookup
/v1/fiat/checkout
Buy prepaid credits by card
/v1/fiat/token
Retrieve bearer token after payment
What agents get from Jentic-routed access to this vendor.
Setup
Wiring The Stall by hand means choosing between signing x402 USDC payloads per call or buying credits through a Stripe checkout and fetching the token, then picking the right capability from hundreds of /cap/ paths. Through Jentic you install once, import it from the API Directory, store the bearer token once, and your agent calls it.
Permission scoping
Every Stall capability is its own path under /cap/, so a rule can pin your agent to the exact capabilities it needs and nothing else. That also bounds spend: you choose the operations it may call, so costlier capabilities like AI image generation or long audio transcription are not included unless you add them.
Credential isolation
Your Stall bearer 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 'verify an email address' or 'get SEC company data for a ticker', and Jentic returns the matching Stall capability with its input schema so the agent calls the right endpoint without paging through the catalog.
Alternatives and complements available in the Jentic catalogue.
Specific to using The Stall API through Jentic.
What authentication does The Stall API use?
Per its OpenAPI spec, the paid /cap/ endpoints accept either an x402 payment, a v2 PaymentPayload sent in the PAYMENT-SIGNATURE header that settles in USDC on Base mainnet, or a bearer token in the Authorization header bought as prepaid credits, with one credit used per call. The catalog, health, stats, payment-method, and fiat checkout endpoints need neither. Through Jentic the bearer token is stored by your own instance and attached at call time.
How do I get a bearer token for The Stall API?
Call POST /v1/fiat/checkout with a bundle of starter, pro, or scale to start a Stripe card purchase, then call GET /v1/fiat/token with the session_id from that checkout to retrieve the token. Send it as a bearer token on any /cap/ endpoint.
Can I see every capability and its price?
Yes. GET /catalog is free and returns all capabilities with names, paths, prices, descriptions, and input and output schemas, which is the quickest way to check what a call costs before making it.
What are the rate limits for The Stall API?
The OpenAPI spec does not specify rate limits. Check https://the-stall.intuitek.ai for current limits before running large batches of paid calls.
Is there a Stall MCP server?
You don't need an MCP server to give your agent The Stall. Jentic connects it directly from the API Directory: import it, store your bearer token once, and your agent finds the one capability it needs by intent instead of loading hundreds of tool definitions into its context.
Can I limit what my agent is allowed to do with The Stall API?
Yes. For example, write a rule that allows only GET /cap/company-intel, GET /cap/equity-fundamentals, and GET /catalog, so the agent can research companies and check prices but cannot spend credits on image generation or any other capability, and every call it makes is logged.
How do I run a company clearance check through Jentic?
Import The Stall from the Jentic API Directory and store your bearer token once. Your agent searches for 'check whether a business is legitimate', gets GET /cap/entity-clearance with its schema, and passes the required name and website. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Call pay-per-use data capabilities for AI agents: SEC EDGAR company intel, stock fundamentals, crypto and DeFi data, domain WHOIS, email verification, and CVE lookups, paid by x402 or prepaid bearer credits.
Use for: I need SEC filing history for a public company ticker, Check whether a business and its website look legitimate before I contact them, Get the analyst price targets for a US stock, Find the registrar and expiry date for a domain
Not supported: Does not handle trade execution, brokerage accounts, or storage of your own data. Use for buying individual data lookups and analyses per call only.
The Stall API from IntuiTek serves 301 pay-per-call data capabilities under /cap/ paths, covering SEC EDGAR company profiles and filings, US equity fundamentals and analyst ratings, crypto and DeFi market data, domain WHOIS and DNS lookups, email verification, CVE lookups, and AI image generation. Each capability call is paid either with an x402 USDC payment on Base mainnet or with a bearer token bought as prepaid credits through a Stripe card checkout. A free catalog endpoint lists every capability with its path, price, and input and output schemas, and no account or vendor API key is required.
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>