Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / AI/ML / Azure / Form Recognizer Client
Form Recognizer Client logo

Microsoft Azure Form Recognizer Client

Browse all Azure APIs
67
AI ReadinessAI-Aware (B)67/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticAI/MLVisionapiKey10 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Train custom form models, analyse forms, layouts, and receipts asynchronously, and retrieve the structured extraction results.

Use for: Train a custom Form Recognizer model from blob folder https://.../forms/, Analyse the invoice at https://.../inv-123.pdf with custom model abc-123, Get the layout of contract.pdf including tables and selection marks, Extract merchant name and total from the receipt at https://.../receipt.jpg

Not supported: Does not transcribe speech, classify or describe arbitrary images, translate text, or run general-purpose OCR - use only to train and run Form Recognizer custom models, layout analysis, and the prebuilt receipt model.

Jentic publishes the only available OpenAPI specification for the Azure Cognitive Services Form Recognizer client (v2.0 preview), keeping it validated and agent-ready. The API extracts structured key-value pairs and tables from forms, layouts, and prebuilt receipts. It supports training custom models on your own labelled forms, listing and deleting those models, analysing forms with a custom model, analysing the layout of any document, and analysing receipts with the prebuilt receipt model. Analysis calls are asynchronous and return a result id you poll until the operation completes.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Form Recognizer Client to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Form Recognizer Client, 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%2Fazure.com%2Fform-recognizer-client" | sh
2

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%2Fazure.com%2Fform-recognizer-client" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Form Recognizer Client API.

Train a custom Form Recognizer model from labelled forms in a SAS-accessible blob folder

List and delete custom Form Recognizer models

Analyse a form with a custom model and poll for the structured key-value result

Analyse the layout (text, tables, selection marks) of an arbitrary document

Extract receipt fields (merchant, total, line items) with the prebuilt receipt model

Retrieve the structured analysis result for any submitted form, layout, or receipt operation

Use Cases

Patterns agents use Form Recognizer Client API for, with concrete tasks.

★ Extract Structured Data from Custom Forms

Operations teams need to convert recurring vendor forms into structured data without writing per-template parsers. Train a custom model with POST /custom/models pointing at a folder of labelled examples, then call POST /custom/models/{modelId}/analyze on each new form. The service returns a result id; GET /custom/models/{modelId}/analyzeResults/{resultId} delivers the extracted key-value pairs once the run finishes.

Train a custom model from blob folder https://contoso.blob.core.windows.net/forms/, then analyse the form at https://contoso.blob.core.windows.net/inbox/inv-2025-01.pdf and return the extracted key-value pairs

Analyse Document Layout for Downstream Pipelines

Document automation pipelines first run layout analysis to capture text, tables, and selection marks before applying domain-specific extraction. POST /layout/analyze submits the document and returns a result id; GET /layout/analyzeResults/{resultId} returns the structured layout once analysis completes, ready to feed the next stage of the pipeline.

Submit contract.pdf to layout analyse, poll the result until succeeded, and return the table cells found on page 2

Receipt Extraction for Expense Workflows

Expense and accounts-payable workflows ingest scanned receipts and need merchant, date, total, tax, and line items. POST /prebuilt/receipt/analyze runs the prebuilt receipt model and returns a result id; GET /prebuilt/receipt/analyzeResults/{resultId} returns the structured fields once analysis completes, ready to be posted to an expense or accounting system.

Analyse the receipt at https://contoso.blob.core.windows.net/receipts/r-001.jpg with the prebuilt receipt model and return merchantName, total, and line items

Agent-Driven Document Pipelines

An AI agent processing inbound documents can train a custom model, route incoming files to the right analyser, and return structured fields to an accounting or CRM workflow through Jentic. Intent search returns the train, analyse, and result endpoints with their schemas; the Ocp-Apim-Subscription-Key is held in your Jentic One instance so the agent only ever holds a short-lived scoped token at call time.

Search Jentic for 'analyse a form with Form Recognizer', execute AnalyzeWithCustomModel for the new file, then call GetAnalyzeFormResult on the returned result id until status is succeeded

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for the azure cognitive services form recognizer client (v2.

METHOD

PATH

DESCRIPTION

POST

/custom/models

Train a custom Form Recognizer model

GET

/custom/models

List custom models

POST

/custom/models/{modelId}/analyze

Analyse a form with a custom model

GET

/custom/models/{modelId}/analyzeResults/{resultId}

Get analyse form result

POST

/layout/analyze

Analyse the layout of a document

GET

/layout/analyzeResults/{resultId}

Get analyse layout result

POST

/prebuilt/receipt/analyze

Analyse a receipt with the prebuilt model

GET

/prebuilt/receipt/analyzeResults/{resultId}

Get analyse receipt result

POST

/custom/models

Train a custom Form Recognizer model

GET

/custom/models

List custom models

POST

/custom/models/{modelId}/analyze

Analyse a form with a custom model

GET

/custom/models/{modelId}/analyzeResults/{resultId}

Get analyse form result

POST

/layout/analyze

Analyse the layout of a document

GET

/layout/analyzeResults/{resultId}

Get analyse layout result

POST

/prebuilt/receipt/analyze

Analyse a receipt with the prebuilt model

GET

/prebuilt/receipt/analyzeResults/{resultId}

Get analyse receipt result

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.

F

Form Recognizer Client

- AI-Aware (B)
67/100
65
Foundational Compliance
63
Developer Experience & Jentic Compatibility
59
AI-Readiness & Agent Experience
94
Agent Usability
50
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
65

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4
83%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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.

59

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C+Signals: 4
82%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

56%

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.

50

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1
50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Form Recognizer by hand means holding the Ocp-Apim-Subscription-Key header, targeting the correct regional Cognitive Services endpoint (for example https://westus2.api.cognitive.microsoft.com), and driving the async analyse pattern where each POST returns a result id you poll until it succeeds. Through Jentic you install once, import the Form Recognizer Client from the API Directory, store the subscription key once, and your agent calls it.

Permission scoping

Form Recognizer puts the model id in the URL path (/custom/models/{modelId}/analyze and /custom/models/{modelId}/analyzeResults/{resultId}), so a rule can pin your agent to one custom model for analysis. You choose the operations it may call, so a destructive one like deleting a custom model is not included unless you add it, and you can keep the agent to training, analyse, and result reads.

Credential isolation

Your Ocp-Apim-Subscription-Key is stored once, encrypted, by your own Jentic One instance and injected at execution time. The raw subscription key never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'analyse a form with Form Recognizer' or 'extract receipt fields', and Jentic returns the matching custom-model, layout, or prebuilt-receipt operation with its input schema so the agent calls the right endpoint without learning the v2.0 path layout.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Amazon Textract

→

AWS document analysis service that extracts text, tables, and forms data from documents.

Choose Textract for AWS-native pipelines. Stay with Form Recognizer when running inside Azure or using prebuilt receipt models.

Alternative

Google Cloud Document AI

→

Google Cloud document understanding service with prebuilt and custom processors.

Choose Document AI for GCP workloads. Stay with Form Recognizer when the rest of your stack runs on Azure Cognitive Services.

Complementary

Azure Cognitive Services Management

→

Provisions and configures the Cognitive Services resource that hosts Form Recognizer.

Use the management client to create the resource and rotate keys; use Form Recognizer Client for the data plane.

Alternative

Google Cloud Vision API

→

General-purpose OCR and image analysis service from Google Cloud.

Choose Cloud Vision for general OCR. Stay with Form Recognizer for structured form, layout, and receipt extraction.

FAQs

Specific to using Form Recognizer Client API through Jentic.

Why is there no official OpenAPI spec for Form Recognizer Client?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Form Recognizer Client via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Form Recognizer API use?

The API uses an API key in the `Ocp-Apim-Subscription-Key` request header (the apim_key scheme). Through Jentic, that key is stored encrypted in your Jentic One instance and injected on each call so the agent never holds the raw subscription key.

Can I train a custom Form Recognizer model with this API?

Yes. Call POST /custom/models with a body that points at a SAS-accessible blob folder containing your labelled forms. The service returns a model id; once training completes, call POST /custom/models/{modelId}/analyze to extract data from new documents of the same template.

How do I get the result of an analyse call?

Analyse calls are asynchronous. The POST /custom/models/{modelId}/analyze, /layout/analyze, and /prebuilt/receipt/analyze endpoints return a result id (in the response headers). Poll the matching GET .../analyzeResults/{resultId} endpoint until the response status is 'succeeded' to retrieve the extracted fields.

What are the rate limits for the Form Recognizer API?

Form Recognizer applies per-resource quotas tied to the Cognitive Services pricing tier (free or standard). On HTTP 429 back off using the Retry-After header. Training jobs are heavier than analyse calls, so issue them serially per resource.

How do I run a Form Recognizer pipeline through Jentic?

Run pip install jentic, then search Jentic with 'analyse a form with Form Recognizer'. Load AnalyzeWithCustomModel, supply the modelId and document URL, and execute. Then call GetAnalyzeFormResult with the returned result id until status is succeeded. The Ocp-Apim-Subscription-Key is sourced from the vault on every call.

Can I limit what my agent is allowed to do with the Azure Form Recognizer API?

Yes. Because you run Jentic One yourself, your own rules decide which Form Recognizer operations the agent may call and which credentials it may use. Since the model id sits in the URL path for POST /custom/models/{modelId}/analyze and GET /custom/models/{modelId}/analyzeResults/{resultId}, you can pin the agent to a single custom model, and you can keep it to training, analysing, and reading results while leaving out a destructive operation like deleting a custom model. Only the operations you explicitly grant are available to the agent.

GET STARTED

Start building with Form Recognizer Client API

Explore with Jentic One
View OpenAPI Document