Install Jentic One Beta

Connect the Code.gov API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Code.gov API, 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%2Fcode.gov%2Fcode-gov" | sh

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%2Fcode.gov%2Fcode-gov" | 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 Code.gov API.

List open-source repositories published by U.S. federal agencies

Retrieve a single repository by its repository id

List participating agencies and get details for one by its acronym

List the programming languages used across the catalog

Check the harvesting status, issues, and fetch results for an agency

GET STARTED

Start building with Code.gov API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Code.gov API for, with concrete tasks.

★ AI agent open-source discovery

An AI agent finds relevant government open-source projects by listing an agency's repositories and filtering by programming language, then retrieves each repository's details. Through Jentic the agent finds these read operations by intent and calls them with the stored API key, without hand-building the catalog query.

List repositories published by the General Services Administration and return their names and languages

Agency code inventory

Researchers building an inventory of federal open-source output list every participating agency and count the repositories each one publishes. The API returns the agency list and per-agency repository data so the inventory can be assembled and refreshed on a schedule.

List all agencies and record how many repositories each one has published

Harvest status monitoring

Because Code.gov harvests each agency's code inventory, teams tracking data freshness check the harvest status, outstanding issues, and last fetch time per agency. The status endpoints report these so a monitor can flag agencies whose data is stale or failing to import.

Check the harvest issues for a given agency and report whether its data imported cleanly

Key Endpoints

12 endpoints — the code.

METHOD

PATH

DESCRIPTION

GET

/repos

List repositories

GET

/repos/{repoId}

Get a repository by id

GET

/agencies

List agencies

GET

/agencies/{agency_acronym}

Get an agency by acronym

GET

/languages

List programming languages

GET

/status/{agencyName}/issues

Get harvest issues for an agency

GET

/repos

List repositories

GET

/repos/{repoId}

Get a repository by id

GET

/agencies

List agencies

GET

/agencies/{agency_acronym}

Get an agency by acronym

GET

/languages

List programming languages

GET

/status/{agencyName}/issues

Get harvest issues for an agency

Why Jentic?

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

Setup

Querying the Code.gov API by hand means supplying an API key on each request, paging through repository results, and matching agency acronyms to their records. Through Jentic you install once, import Code.gov from the API Directory, store the key once, and your agent calls it.

Permission scoping

Every Code.gov operation is a read, and the agency acronym or repository id sits in the URL path, so a rule can pin your agent to one agency's repositories. You choose the operations it may call, so the agent only reads the catalog data you allow.

Credential isolation

Your Code.gov API key is stored once, encrypted, by your own Jentic One instance and injected at request time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list an agency's repositories' or 'list programming languages', and Jentic returns the matching Code.gov operation with its input schema so the agent calls the right endpoint without reading the API docs.

FAQs

Specific to using Code.gov API through Jentic.

Is there a Code.gov MCP server?

You don't need an MCP server to connect your agent to the Code.gov API. Jentic connects it directly from the API Directory: import Code.gov, store your API key once, and your agent lists repositories, agencies, and languages on demand.

Can I limit what my agent is allowed to do with the Code.gov API?

Yes. Because every operation is read-only, you can allow your agent just the repository and language lookups and leave the status endpoints out. The agency acronym sits in the URL path, so you can even scope it to a single agency, and every call the agent makes is logged.

What authentication does the Code.gov API use?

The Code.gov API requires an API key from api.data.gov, sent with each request. Through Jentic the key is stored once by your self-hosted instance and injected at call time, so it never reaches the agent's context.

Can I list all repositories from one agency with the Code.gov API?

Yes. Look up the agency by its acronym, then list repositories filtered to that agency to get its published open-source projects with their languages and descriptions. Page through the results for agencies with large catalogs.

What are the rate limits for the Code.gov API?

The OpenAPI spec does not specify rate limits. Code.gov uses api.data.gov keys, which apply their own per-key hourly limits, so check your key's quota before large crawls.

How do I connect the Code.gov API to my AI agent?

Search the Jentic API Directory for the Code.gov operation you need, such as listing an agency's repositories, and import it. To run it on your own infrastructure, install Jentic One from its GitHub repo, then your agent calls the API with your API key injected at execution time.

Code.gov API

Name: Code.gov API
Brand: Code.gov
Availability: InStock

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey12 EndpointsREST

For Agents

List and look up open-source repositories published by U.S. federal agencies, retrieve agency details, list programming languages, and check catalog harvesting status.

Use for: Find open-source repositories from a specific federal agency, Look up a repository by its id, List all agencies in the Code.gov catalog, See which programming languages are used across government code

Not supported: Does not host code, accept repository submissions, or run source-control operations like commits or pull requests. Use for reading the Code.gov catalog of agencies, repositories, and languages only.

The Code.gov API provides programmatic access to the United States government's open-source software catalog: it lists code repositories published by federal agencies, returns repository and agency details, reports harvesting status, and enumerates the programming languages in use. Use it to discover and analyze government open-source projects.

Jentic One on Github View OpenAPI Document