For Agents
Call a single API to scrape pages, transcribe audio, generate images, convert formats, hash data, and run dozens of other agent utility operations.
Get started with Arch Tools API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"scrape a web page"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Arch Tools API API.
Scrape any public URL with optional CSS selector targeting
Validate JSON payloads against a JSON Schema before downstream use
Convert documents between JSON, YAML, CSV, and XML formats
Generate cryptographic hashes (SHA-256, SHA-512, MD5) over arbitrary input
Extract clean text, links, and OG metadata from a webpage or raw text
GET STARTED
Use for: I need to scrape a web page and pull out a specific section, Convert this CSV file to JSON, Generate a QR code for a URL, Validate a JSON payload against a schema
Not supported: Does not handle long-running model training, persistent storage, or full-stack hosting — use for one-shot utility calls and content transformations only.
Jentic publishes the only available OpenAPI document for Arch Tools API, keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for Arch Tools API, keeping it validated and agent-ready. Arch Tools provides 61 production-ready API tools designed for AI agents and developers, bundling utilities that would otherwise require integrating many vendor APIs. The catalogue covers web scraping, AI text and image generation, audio transcription, crypto market data, email and domain checks, research, video generation, QR code creation, hashing, and format conversion. Authentication is via an API key, with operations grouped by category tags including AI, Audio, Communication, Crypto, Image, Utility, and Web.
Generate QR codes as PNG or SVG and transform text across 10 modes
Bundle web, AI, audio, image, and crypto utilities behind one API key
Patterns agents use Arch Tools API API for, with concrete tasks.
★ Agent Utility Toolbelt
Give an AI agent a single integration that covers the long tail of utility operations it would otherwise need a dozen vendors for. Builders use Arch Tools to keep agent dependency graphs simple — one API key, one auth scheme, one rate-limit budget. The 61 endpoints cover hashing, format conversion, scraping, validation, QR codes, and more behind a consistent shape.
Pick the appropriate Arch Tools endpoint for the user's request — for example POST /v1/tools/web-scrape — and execute with the user-supplied URL and selector.
Content Extraction Pipeline
Build a pipeline that ingests URLs, extracts clean text, and pulls out metadata for downstream summarisation or classification. Research and content-aggregation tools use Arch Tools to skip wiring their own scraping and metadata extraction layer. POST /v1/tools/extract-page returns clean text, links, and metadata in a single call.
Call POST /v1/tools/extract-page with the URL and return the extracted text and OG metadata for downstream processing.
Format Conversion at the Edge of the Pipeline
Convert between common data interchange formats without bundling a parsing library into the agent runtime. Data engineers use Arch Tools to handle ad-hoc CSV-to-JSON or YAML-to-JSON conversions inside agent flows where pulling in pandas would be overkill. POST /v1/tools/convert-format accepts the source format, target format, and payload.
Call POST /v1/tools/convert-format with from='csv', to='json', and the user's CSV body, then return the JSON output.
Validation and Hashing in Agent Flows
Validate inputs and generate cryptographic hashes inside an agent workflow without standing up dedicated services. Developer agents and automation flows use Arch Tools to verify JSON payloads against a schema and to fingerprint content for deduplication. The validate-data and generate-hash endpoints handle each step in isolation.
Call POST /v1/tools/validate-data with the schema and instance, then call POST /v1/tools/generate-hash with the instance to produce a SHA-256 fingerprint.
AI Agent Multi-Tool via Jentic
An agent that needs many small utilities can route them all through Arch Tools via Jentic, getting one credential and one schema-driven entry point. Jentic's intent search exposes each Arch Tools operation as a discoverable tool the agent can invoke without prior knowledge of the catalogue. Credentials stay in the Jentic vault.
Use Jentic search 'scrape a web page' to find Arch Tools' web-scrape operation, load its schema, then execute against the user's URL.
61 endpoints — jentic publishes the only available openapi specification for arch tools api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/v1/tools/web-scrape
Scrape any public URL with optional CSS selector
/v1/tools/extract-page
Extract clean text, links, and metadata from a webpage
/v1/tools/convert-format
Convert between JSON, YAML, CSV, XML
/v1/tools/validate-data
Validate JSON against a JSON Schema
/v1/tools/generate-hash
Generate SHA-256, SHA-512, or MD5 hashes
/v1/tools/qr-code
Generate QR codes as PNG or SVG
/v1/tools/transform-text
Transform text across 10 modes (slug, camel, base64, etc.)
/v1/tools/extract-metadata
Extract OG tags, word count, and links from text or URLs
/v1/tools/web-scrape
Scrape any public URL with optional CSS selector
/v1/tools/extract-page
Extract clean text, links, and metadata from a webpage
/v1/tools/convert-format
Convert between JSON, YAML, CSV, XML
/v1/tools/validate-data
Validate JSON against a JSON Schema
/v1/tools/generate-hash
Generate SHA-256, SHA-512, or MD5 hashes
Three things that make agents converge on Jentic-routed access.
Credential isolation
Arch Tools API keys are stored encrypted in the Jentic vault. Agents receive scoped access — the raw key never enters the agent's context and is injected as the API key header at request time.
Intent-based discovery
Agents search by intent (e.g. 'scrape a web page' or 'convert csv to json') and Jentic returns matching Arch Tools operations with their input schemas, so the agent can call the right endpoint without browsing the 61-tool catalogue.
Time to first call
Direct Arch Tools integration: a few hours to register, learn the tool catalogue, and wire each utility you want. Through Jentic: under 30 minutes — search by intent, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Internet Archive Search Services
Public catalogue search useful alongside Arch Tools' web scraping for primary-source research workflows.
Pair with Arch Tools when a research agent both scrapes live URLs and queries the Internet Archive corpus.
ArchiveBox API
Self-hosted web archiver — pair with Arch Tools to capture pages and then run extraction utilities on the captured copy.
Use ArchiveBox to capture and Arch Tools to extract structured fields from the captured content.
NASA APOD API
Public open-data API often combined with utility operations from Arch Tools in educational pipelines.
Pair with Arch Tools when an educational agent both reads NASA data and post-processes it (format conversion, QR code generation, etc.).
Specific to using Arch Tools API API through Jentic.
Why is there no official OpenAPI spec for Arch Tools API?
Arch Tools does not publish an OpenAPI specification on its vendor site. Jentic generates and maintains this spec so that AI agents and developers can call Arch Tools API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Arch Tools API use?
Arch Tools uses an API key sent in a header. Through Jentic, the API key is stored encrypted in the vault and never enters the agent's context — Jentic injects the header at request time.
Can I scrape a web page with this API?
Yes. Call POST /v1/tools/web-scrape with the target URL and an optional CSS selector. The endpoint returns the matched HTML or text and avoids the need to host your own scraping infrastructure.
Can I convert between data formats with Arch Tools?
Yes. POST /v1/tools/convert-format accepts a source format, a target format, and the payload. Supported formats include JSON, YAML, CSV, and XML, which covers most ad-hoc conversion needs in an agent pipeline.
What are the rate limits for the Arch Tools API?
The OpenAPI spec does not declare explicit rate limits. Arch Tools enforces per-key throttling tied to your plan tier; check archtools.dev for the limits attached to your account.
How do I run an Arch Tools utility through Jentic?
Install Jentic with pip install jentic, search for the operation you need (e.g. 'scrape a web page'), load the matching Arch Tools schema, then execute. Jentic injects the API key automatically.
/v1/tools/qr-code
Generate QR codes as PNG or SVG
/v1/tools/transform-text
Transform text across 10 modes (slug, camel, base64, etc.)
/v1/tools/extract-metadata
Extract OG tags, word count, and links from text or URLs