Install Jentic One Beta

Connect the Frontera Signal API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Frontera Signal 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%2Ffronterasignal.com%2Ffronterasignal" | 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%2Ffronterasignal.com%2Ffronterasignal" | 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 Frontera Signal API.

Read weekly building-permit counts and the building-input price basket for Hidalgo and Cameron counties

List new commercial projects near a street address with the owner and filed cost

Pull a Hidalgo County parcel record for a given address

Track filed cost per square foot and housing supply trends by county

Read shelf prices for common building materials as low, high, and unit ranges

GET STARTED

Start building with Frontera Signal API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Frontera Signal API for, with concrete tasks.

★ AI Agent Construction-Data Lookup

An AI agent reaches Frontera Signal through Jentic to answer construction-market questions about the Rio Grande Valley without wiring the x402 payment flow itself. It searches by intent, receives the matching operation and its input schema, and executes the read with payment settled by its own instance. This lets the agent cite a fresh, dated figure rather than guess at regional permit or price trends.

Search Jentic for 'weekly building permits for Hidalgo County', load the GET /api/v1/series/permits-weekly schema, and execute it to read the latest week

Commercial Project Monitoring

A real-estate or construction team tracks new commercial projects as they are filed across Hidalgo, Cameron, Starr, and Willacy counties. Frontera Signal lists projects near a given street address and the broader commercial filings by county, each with the owner and filed cost, so the agent can surface new activity in a target area. Every record carries an as_of date and a stale flag so the team knows how current the filing is.

Call GET /api/v1/nearby with an address and city to list nearby commercial projects, then GET /api/v1/projects filtered by county to track new filings

Parcel and Cost Due Diligence

Before pricing or bidding on work, an agent pulls the Hidalgo County parcel record for an address and the filed cost per square foot for the area. Frontera Signal returns construction cost as low, high, and unit ranges with an approx flag on rounded readings, so the agent can ground an estimate in filed data rather than a guess. The parcel-match endpoint confirms whether a record exists before a paid lookup is made.

Call GET /api/v1/parcel with an address and city for the parcel record, then GET /api/v1/cost-per-sqft to read filed construction cost for the area

Building Material Price Tracking

A contractor or estimator watches shelf prices for common building materials in the Rio Grande Valley. Frontera Signal returns each material price as a low, high, and unit range with an as_of date, so an agent can detect when a basket item moves and flag it. Pairing the materials feed with the weekly cost-basket series shows both the shelf price and the broader building-input trend.

Call GET /api/v1/materials to read current shelf prices for common building materials as low, high, and unit ranges

Key Endpoints

18 endpoints — the frontera signal api serves construction market data for the rio grande valley of south texas, covering hidalgo, cameron, starr, and willacy counties.

METHOD

PATH

DESCRIPTION

GET

/api/v1

Free catalog of paid endpoints and their prices

GET

/api/v1/snapshot

City construction snapshot

GET

/api/v1/projects

New commercial projects by county

GET

/api/v1/nearby

Commercial projects near an address

GET

/api/v1/parcel

Parcel record for an address

GET

/api/v1/cost-per-sqft

Filed cost per square foot

GET

/api/v1/series/permits-weekly

Building permits by week

GET

/api/v1/materials

Building material shelf prices

GET

/api/v1

Free catalog of paid endpoints and their prices

GET

/api/v1/snapshot

City construction snapshot

GET

/api/v1/projects

New commercial projects by county

GET

/api/v1/nearby

Commercial projects near an address

GET

/api/v1/parcel

Parcel record for an address

GET

/api/v1/cost-per-sqft

Filed cost per square foot

GET

/api/v1/series/permits-weekly

Building permits by week

GET

/api/v1/materials

Building material shelf prices

Why Jentic?

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

Setup

Wiring Frontera Signal by hand means handling its x402 payment flow yourself: catching the 402 response, decoding the base64 PAYMENT-REQUIRED header, and paying in USDC on Base before each paid call. Through Jentic you install once, import Frontera Signal from the API Directory, and your agent calls it while your instance settles the payment.

Permission scoping

Every Frontera Signal operation is a read-only GET, so a rule can limit your agent to the data pulls it needs, such as the weekly permits series or a parcel lookup, and nothing else. You choose which operations it may call, so a broad snapshot or the commercial-projects feed is not reachable unless you add it.

Credential isolation

Frontera Signal needs no API key or account: it is paid per call over x402, so the only thing Jentic holds is the payment configuration for your own instance. That configuration stays out of the agent's prompt, logs, and context, and your instance settles each call at execution time.

Intent-based discovery

Agents search Jentic by intent such as 'this week's building permits' or 'parcel record for an address', and Jentic returns the matching Frontera Signal operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Frontera Signal API through Jentic.

What authentication does the Frontera Signal API use?

The Frontera Signal API requires no API key and no account. Its paid endpoints charge per call over the x402 protocol in USDC on the Base network: the server answers an unpaid request with a 402 status and a base64 PAYMENT-REQUIRED header, and the client retries with a PAYMENT-SIGNATURE header. The catalog, health, and changelog endpoints are free. Through Jentic the payment configuration is held by your own Jentic One instance, so the agent never handles it.

What are the rate limits for the Frontera Signal API?

The OpenAPI spec does not specify rate limits. Pricing is per call in USDC on Base, and the free catalog endpoint lists the price of every paid endpoint so an agent can read the cost before it spends. See https://fronterasignal.com/terms/ for current terms.

Can I pull weekly building permits with the Frontera Signal API?

Yes. The GET /api/v1/series/permits-weekly operation returns building permits by week for the Rio Grande Valley, with optional from and to bounds, and GET /api/v1/series/permits-monthly returns the monthly housing-permit series. Each reading carries an as_of date, an age in days, and a stale flag so the agent knows how fresh the figure is.

Is there a Frontera Signal MCP server?

You don't need an MCP server to give your agent Frontera Signal. Jentic connects it directly from the API Directory: import it and your agent calls the construction-data endpoints on demand, discovering each operation's schema when it needs it rather than loading a separate server's tool definitions into context.

How do I pull a parcel record with the Frontera Signal API through Jentic?

Search Jentic for 'parcel record for an address', and it returns the Frontera Signal parcel operation with its input schema. Load the schema and execute GET /api/v1/parcel with the address and city, with the x402 payment settled by your instance at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. Because every operation is a read-only GET, write a rule that allows only the specific pulls a task needs, for example the weekly permits series and a single parcel lookup, and the agent cannot reach the other series or the commercial-projects feed. Every call runs through your own instance, so each one is logged for you to review.

Frontera Signal API

AI ReadinessFoundational (C+)59/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentCompany Datanone18 EndpointsREST

For Agents

Read construction market data for the Rio Grande Valley of South Texas: weekly permits, building-input prices, housing supply, labor conditions, commercial projects, parcel records, and material prices. All operations are read-only GETs paid per call over x402, with no API key or account.

Use for: Get this week's building permits for Hidalgo County, Find new commercial construction projects near an address, Look up the parcel record for a Rio Grande Valley address, Check filed cost per square foot in Cameron County

Not supported: Does not handle permit filing, construction project management, or lending. Use for reading Rio Grande Valley construction market data only.

The Frontera Signal API serves construction market data for the Rio Grande Valley of South Texas, covering Hidalgo, Cameron, Starr, and Willacy counties. It returns weekly building permits, building-input price baskets, housing supply and labor conditions, new commercial projects near a street address, company track records with trade licenses, filed cost per square foot, Hidalgo County parcel records, and shelf prices for common building materials. Every reading carries an as_of date, an age in days, a cadence, and a stale flag so a reader knows how fresh it is. The paid endpoints charge per call over the x402 protocol in USDC on the Base network, with no account and no API key.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

25%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

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

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

67%

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.

AI-Readiness & Agent Experience

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

Grade: FSignals: 4

17%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

56%

OperationId Quality

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

49%

Summary Coverage

Coverage of summaries across operations/tags/info.

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

94%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Frontera Signal API to your agent

Capabilities

Start building with Frontera Signal API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Frontera Signal API

Jentic AI Readiness Score

Frontera Signal API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness