Apisetu Agricultural Scientists Recruitment Board

Name: Agricultural Scientists Recruitment Board API
Brand: Agricultural Scientists Recruitment Board
Availability: InStock

Browse all Apisetu APIs

★ Only Publicly Available OpenAPI DocumentEducationAssessmentapiKey1 Endpoints

Install Jentic One Beta

Connect the Agricultural Scientists Recruitment Board to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Agricultural Scientists Recruitment Board, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Agricultural Scientists Recruitment Board API.

Pull a candidate's ASRB NET merit certificate as a verifiable digital document

Authenticate certificate requests with the X-APISETU-APIKEY and X-APISETU-CLIENTID header pair

Submit candidate identifiers in a POST body to /mrcer/certificate and receive a DigiLocker-compatible payload

GET STARTED

Start building with Agricultural Scientists Recruitment Board API

Explore with Jentic

View OpenAPI Document

For Agents

Fetch ASRB NET merit certificates for a candidate as a verified digital document via API Setu and DigiLocker.

Use for: Retrieve an ASRB NET merit certificate for a candidate, Verify whether a candidate qualified the ASRB NET-I or NET-II 2019 exam, Pull a digital ASRB merit certificate into a DigiLocker workflow, Check the authenticity of an Agricultural Scientists Recruitment Board certificate

Not supported: Does not handle exam registration, application submission, or non-NET ASRB recruitment categories - use for retrieving NET-I and NET-II 2019 merit certificates only.

Use Cases

Patterns agents use Agricultural Scientists Recruitment Board API for, with concrete tasks.

★ Agricultural Recruitment Verification

Government bodies and ICAR-affiliated employers verifying candidates for agricultural scientist positions can pull the official ASRB NET merit certificate directly from API Setu rather than asking applicants to upload PDFs. The /mrcer/certificate endpoint returns a DigiLocker-compatible record that is signed at source, removing the need for manual document checks.

Call POST /mrcer/certificate with the candidate's roll number and registration details, receive the signed merit certificate, and attach it to a recruitment record.

DigiLocker Issuer Integration

DigiLocker partner applications that surface academic and employment qualifications can list ASRB NET merit certificates alongside other government documents. Integrating the ASRB endpoint lets users fetch their certificate once and reuse it across job applications, scholarship submissions, and academic admissions without re-uploading.

Authenticate with X-APISETU-APIKEY and X-APISETU-CLIENTID, request the candidate's ASRB merit certificate, and store the issued document reference in the user's DigiLocker wallet.

Academic Records Aggregation

EdTech platforms and academic CV builders that compile a candidate's verified credentials can pull the ASRB NET merit certificate as one component of a wider portfolio. Because the source is a government-issued document, downstream consumers can trust the qualification claim without additional verification steps.

Retrieve the ASRB merit certificate for a verified candidate and include it in a credentials bundle returned to a hiring portal.

AI Agent Credential Verification

An AI agent assisting with government recruitment workflows can use Jentic to call the ASRB endpoint without managing API Setu API key rotation directly. Jentic handles credential isolation and surfaces the single available operation through intent search, so the agent only needs to request the certificate and pass through the candidate identifiers.

Search Jentic for 'fetch ASRB merit certificate', load the operation schema, and execute it with the candidate's roll number on behalf of a recruitment agent workflow.

Key Endpoints

1 endpoints — the agricultural scientists recruitment board (asrb) api integrates with india's digilocker platform to issue digital merit certificates for the national eligibility test (net-i and net-ii).

METHOD

PATH

DESCRIPTION

POST

/mrcer/certificate

Issue an ASRB NET merit certificate for a qualified candidate.

POST

/mrcer/certificate

Issue an ASRB NET merit certificate for a qualified candidate.

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your API Setu 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 'retrieve an ASRB NET merit certificate', and Jentic returns the matching ASRB operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Agricultural Scientists Recruitment Board API through Jentic.

What authentication does the ASRB API use?

The ASRB API requires two header credentials: X-APISETU-APIKEY (the API Setu API key) and X-APISETU-CLIENTID (the integrator's client ID). Both are issued by API Setu after onboarding. When called through Jentic, these credentials stay encrypted in your Jentic One instance and never enter the agent's prompt context.

Can I retrieve other ASRB exam results with this API?

No. The spec exposes a single operation, POST /mrcer/certificate, scoped to NET-I and NET-II 2019 merit certificates. Other ASRB exam cycles or recruitment categories are not part of this API's surface.

What are the rate limits for the ASRB API?

API Setu does not publish a global limit in the OpenAPI spec; rate limits are negotiated per integrator during DigiLocker onboarding. Treat the operation as low-volume and cache fetched certificates rather than re-requesting on every page load.

How do I fetch a candidate's merit certificate through Jentic?

Run pip install jentic, then search Jentic for 'ASRB merit certificate', load the schema for POST /mrcer/certificate, and execute the call with the candidate's identifiers. Jentic injects the X-APISETU-APIKEY and X-APISETU-CLIENTID headers from your stored credentials. Run it through Jentic One, the self-hosted execution layer.

Is the ASRB API free to use?

API Setu is a Government of India platform and the ASRB endpoint is provided to onboarded integrators without per-call charges. You must, however, complete the API Setu and DigiLocker partner onboarding to receive credentials.

Does the ASRB API return a verifiable document or just data?

POST /mrcer/certificate returns a DigiLocker-compatible certificate payload that is digitally signed at source. Downstream systems can present it as a verified government document rather than as ad-hoc JSON.

Can I limit what my agent is allowed to do with the ASRB API?

Yes. The ASRB API exposes a single operation, POST /mrcer/certificate, which takes its candidate lookup fields in the request body, and Jentic One runs self-hosted so your own rules decide which operations and credentials the agent may use. You allowlist just that one certificate-fetch operation, so the agent can only pull a candidate's ASRB NET merit certificate and nothing else. Your API Setu key and client ID stay stored by your own instance and are injected at execution time, so the agent scopes to exactly the calls you permit.