Install Jentic One Beta

Connect the Electronics Architect API to your agent

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

Solve a power tree for input current, efficiency, and dissipation at every stage

Run Monte Carlo tolerance analysis across a design's corners

Check a design's derating against the NASA GSFC or IPC-9592 standard

Store, version, and compare cloud designs

Export a BOM, the design JSON, or the solved result

GET STARTED

Start building with Electronics Architect API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Electronics Architect API for, with concrete tasks.

★ Agent-run power-design checks

An engineering agent verifies a power design without a desktop tool. Through Jentic the agent validates the design's structure, solves one tolerance corner for the current, efficiency, and dissipation of each stage, and runs a derating check against the NASA GSFC or IPC-9592 standard, returning numbers an engineer can act on. The result carries a fingerprint the agent can later re-verify.

Validate a power-tree design, solve one corner, and run an IPC-9592 derating check, then report the per-stage dissipation

Tolerance analysis before a board spin

A designer wants the spread, not just the nominal case. The Monte Carlo operation runs a tolerance analysis across the design's corners as a metered job, so a workflow can quantify how converter efficiency and dissipation vary before committing a board. Starting a job runs the first slice immediately and the rest are polled.

Start a Monte Carlo job on a design and poll it until the tolerance analysis across corners is complete

Design from a plain-English brief

An agent turns a requirement into a starting design. The synthesize operation generates a power design from a plain-English brief, and the solve and review operations then compute the numbers and explain what they mean and what to change. A design can be stored, versioned, and exported as a BOM for sourcing.

Synthesize a power design from a brief, solve it, and export the BOM for the resulting design

Key Endpoints

25 endpoints — the electronics architect api solves power-architecture designs: you describe a power tree and its server-side solver returns the converged numbers, the input current, efficiency, and dissipation of every stage, with load-dependent converter efficiency, tolerance corners, and thermal estimates in one pass.

METHOD

PATH

DESCRIPTION

POST

/v1/designs/solve

Solve one tolerance corner

POST

/v1/designs/monte-carlo

Run Monte Carlo tolerance analysis

POST

/v1/designs/derating

Run derating analysis against a standard

POST

/v1/designs

Create a cloud design

POST

/v1/designs/{id}/exports

Export a BOM or the solved result

POST

/v1/designs/compare

Compare two designs

POST

/v1/designs/validate

Validate a design's structure

POST

/v1/ai/synthesize

Synthesize a design from a brief

POST

/v1/designs/solve

Solve one tolerance corner

POST

/v1/designs/monte-carlo

Run Monte Carlo tolerance analysis

POST

/v1/designs/derating

Run derating analysis against a standard

POST

/v1/designs

Create a cloud design

POST

/v1/designs/{id}/exports

Export a BOM or the solved result

POST

/v1/designs/compare

Compare two designs

POST

/v1/designs/validate

Validate a design's structure

POST

/v1/ai/synthesize

Synthesize a design from a brief

Why Jentic?

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

Setup

Wiring the Electronics Architect API by hand means handling its bearer API key, managing metered Monte Carlo jobs that you poll for each slice, and parsing the solved power-tree result yourself. Through Jentic you install once, import Electronics Architect from the API Directory, store the key once, and your agent calls it.

Permission scoping

Electronics Architect puts the design and job id in the URL path (/designs/{id}/... and /jobs/{id}), so a rule can pin your agent to the solve and analysis operations it needs. Deleting a design or cancelling a job is not included unless you add it.

Credential isolation

Your Electronics Architect 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 'solve a power tree' or 'run a derating check', and Jentic returns the matching Electronics Architect operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using Electronics Architect API through Jentic.

What authentication does the Electronics Architect API use?

The Electronics Architect API authenticates with a bearer API key per its OpenAPI spec: you create a key in the editor's developer settings and send it as `Authorization: Bearer ea_live_...`. The OpenAPI document itself is public. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's context.

Is there an Electronics Architect MCP server?

You don't need a separate MCP server to give your agent the Electronics Architect API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the solve, derating, and export operations on demand without loading another server's tool definitions into its context.

Can I run a derating analysis with the Electronics Architect API?

Yes. The derating operation checks a design against the NASA GSFC or IPC-9592 standard, and alongside it you can solve a single tolerance corner or run a full Monte Carlo tolerance analysis as a metered job you poll for results. Each solved result carries a fingerprint you can later re-verify.

What are the rate limits for the Electronics Architect API?

The OpenAPI spec does not publish specific rate limits, though the account endpoint reports this month's usage against your plan. Check the provider's documentation at https://electronics-architect.com for the current limits on your plan.

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

Yes. Write a rule that allows only the solve and analysis operations your agent needs, so it can compute and export results but cannot delete a stored design or cancel a job. Every call it makes is logged.

How do I solve a power tree with the Electronics Architect API through Jentic?

Search Jentic for 'solve a power tree' and it returns the solve operation with its input schema; your agent passes the design and reads back the per-stage current, efficiency, and dissipation. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Electronics Architect API

AI ReadinessFoundational (D)47/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsTesting Qabearer25 EndpointsREST

For Agents

Solve a power tree for the current, efficiency, and dissipation of every stage, run Monte Carlo and derating checks, and store, compare, or export designs through one metered API.

Use for: Solve this power tree and return the efficiency of each stage, Run a Monte Carlo tolerance analysis on my design, Check whether my design passes IPC-9592 derating, Compare two versions of a design and show what changed

Not supported: Does not handle PCB layout, schematic capture, or component purchasing. Use for solving and analyzing power-architecture designs only.

The Electronics Architect API solves power-architecture designs: you describe a power tree and its server-side solver returns the converged numbers, the input current, efficiency, and dissipation of every stage, with load-dependent converter efficiency, tolerance corners, and thermal estimates in one pass. It runs Monte Carlo tolerance analysis and derating checks against the NASA GSFC and IPC-9592 standards, stores and versions cloud designs, compares two designs, and exports a BOM or the solved result. It can also review a solved design or synthesize one from a plain-English brief, using the same solver behind the editor an engineer opens to edit, export, and share.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

81%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

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: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

54%

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

49%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

55%

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: B-Signals: 1

60%

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: CSignals: 1

56%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Electronics Architect API to your agent

Capabilities

Start building with Electronics Architect API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Electronics Architect API

Jentic AI Readiness Score

Electronics Architect 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