Install Jentic One Beta

Connect the Basile API to your agent

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

Search French companies by activity, legal form, and location with include and exclude filters

Search business contacts by job title, seniority, skills, and school

Count the matching records for free before spending credits on an extraction

Export matched people or companies as an enriched CSV

Pull a raw company or contact record by its id

GET STARTED

Start building with Basile API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Basile API for, with concrete tasks.

★ Build a French prospecting list through Jentic

Assemble a targeted list of French companies or decision-makers without hand-wiring the search API. The agent applies include and exclude filters, checks the free match count to refine them, and exports the result as a CSV. Through Jentic the search operation is discovered by intent and called with its input schema, so the agent builds the list in one flow.

Search companies with POST /companies/find using activity and city filters, then export the matches with POST /companies/export

Company firmographic lookup

Enrich a known French company with firmographic data sourced from the legal registry, LinkedIn, and Google My Business. The agent searches by name or filters, then pulls the full record, so it can attach legal form, activity, and rating to a CRM entry.

Search with POST /companies/find, then fetch the full record with GET /companies/{id}

Decision-maker discovery

Find the right people at target companies by job title, seniority, skills, and school. The agent filters the contact database and reads the match count before extracting, so outreach lists stay precise and credit spend stays controlled.

Search contacts with POST /people/find filtered by job title and seniority, then review the match count

Free count before extraction

Avoid wasting credits on an export that returns too many or too few records. Basile returns the number of matching records for free, so the agent can tighten include and exclude filters against the count and only export once the match set is right.

Run POST /people/find to read the free match count, then export the final set with POST /people/export

Key Endpoints

10 endpoints — the basile api searches a french b2b database of about 26.

METHOD

PATH

DESCRIPTION

POST

/people/find

Search business contacts

POST

/people/export

Export matched contacts as a CSV

GET

/people/{id}

Get a raw contact record

POST

/companies/find

Search companies

POST

/companies/export

Export matched companies as a CSV

GET

/companies/{id}

Get a raw company record

GET

/companies/activity-suggest

Suggest company activities for filtering

GET

/people/roles/suggest

Suggest job titles for filtering

POST

/people/find

Search business contacts

POST

/people/export

Export matched contacts as a CSV

GET

/people/{id}

Get a raw contact record

POST

/companies/find

Search companies

POST

/companies/export

Export matched companies as a CSV

GET

/companies/{id}

Get a raw company record

GET

/companies/activity-suggest

Suggest company activities for filtering

GET

/people/roles/suggest

Suggest job titles for filtering

Why Jentic?

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

Setup

Wiring Basile by hand means learning its API key header, its include and exclude filter system, and the two-step count-then-export flow. Through Jentic you install once, import Basile from the API Directory, store the key once, and your agent calls it.

Permission scoping

Basile carries its search filters in the request body, so a rule bounds which operations your agent may call, not which records it may see. You can allow the search and count operations while leaving CSV export out unless you add it, so the agent explores matches without pulling paid exports.

Credential isolation

Your Basile API 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 'find French companies by activity' or 'export matching contacts', and Jentic returns the matching Basile operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Basile API through Jentic.

What authentication does the Basile API use?

The Basile API authenticates with an API key sent in the `Authorization` header per its OpenAPI spec. Its search, export, and lookup operations all require the key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

Can I count matching records before exporting with the Basile API?

Yes. Both the people and company search operations return the number of matching records for free, so your agent can refine the include and exclude filters before spending credits on a CSV export.

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

Yes. Write a rule that allows only the people and company search operations, so your agent can explore and count matches but cannot trigger a credit-consuming CSV export unless you add that operation. Basile keeps its filters in the request body, so rules bound which operations run, not which records are returned.

What are the rate limits for the Basile API?

The OpenAPI spec does not specify rate limits. Check the Basile documentation at https://docs.basile.cc for current limits before running large extraction jobs.

Is there a Basile MCP server?

You don't need an MCP server to give your agent Basile. Jentic connects it directly from the API Directory: import it, store your key once, and your agent runs the search, count, and export operations on demand. That also keeps extra tool definitions out of the agent's context.

How do I build a French prospecting list with the Basile API through Jentic?

Search Jentic for 'find French companies by activity and location' and it returns the Basile search operation with its input schema. Your agent applies include and exclude filters, reads the free match count, and exports the result as a CSV. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Basile Cc Basile API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentContact EnrichmentapiKey10 EndpointsREST

For Agents

Search a French B2B database of about 26.8 million companies and 29.5 million business contacts, filter by firmographic and professional attributes, count matches for free, and export enriched people or company records as CSV across 10 endpoints.

Use for: Find all French companies in a given city and activity, Search for decision-makers by job title and seniority, Count how many contacts match my filters before exporting, Export a list of matching companies as a CSV

Not supported: Does not send email or SMS campaigns, run outreach sequences, or verify email deliverability. Use for searching and exporting French company and contact data only.

The Basile API searches a French B2B database of about 26.8 million companies and 29.5 million business contacts built from the national legal registry, LinkedIn profiles, and Google My Business listings. It filters people by job title, seniority, skills, and school and companies by activity, legal form, and location, using an include and exclude system with a free match count before any extraction. Matched records export as an enriched CSV, and a single company or contact record can be pulled by its id.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

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).

50%

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

10%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

40%

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: C-Signals: 4

60%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

52%

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.

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).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

65%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Basile API to your agent

Capabilities

Start building with Basile API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Basile Cc Basile API

Jentic AI Readiness Score

Basile 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