Install Jentic One Beta

Connect the DreamFactory SQL Server to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DreamFactory SQL Server, 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%2Fdreamfactory.com%2Fdreamfactory" | 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%2Fdreamfactory.com%2Fdreamfactory" | 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 DreamFactory SQL Server API.

Read and write records in any SQL Server table with filtering, sorting, and pagination

Retrieve table schema definitions and create or replace tables through the schema endpoints

Drop a table or patch its structure without a direct database connection

Call stored procedures by name and read their result sets

GET STARTED

Start building with DreamFactory SQL Server API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use DreamFactory SQL Server API for, with concrete tasks.

★ Agent querying a SQL Server database

An AI agent connected through Jentic can answer questions against a SQL Server database without writing SQL or holding a database connection. It lists the available tables, reads rows from the relevant one with a filter, and returns the result as JSON, so a natural-language question becomes a REST read against the auto-generated table endpoints.

List the tables the service exposes, read rows from the Application.Cities table filtered to one country, and return the first 50 rows.

Expose a legacy database to applications

DreamFactory generates REST endpoints for every table in a SQL Server database, so a legacy datastore can serve modern apps without a custom backend. An application can insert, update, and read records through the table endpoints, using the same filtering and pagination parameters across every table rather than bespoke queries per screen.

Insert a new record into a table, then read it back by its primary key to confirm the write succeeded.

Schema introspection and migration

The schema endpoints let a tool read a table's definition, create new tables, and replace or patch existing structures over HTTP. A migration agent can retrieve the current schema for a set of tables, create a new table with the required fields, and verify the definition, keeping structural changes scriptable and auditable.

Retrieve the schema for an existing table, create a new table with matching fields, and confirm the new table's definition.

Invoke stored procedures and functions

DreamFactory exposes a database's stored procedures and functions as callable endpoints, so server-side logic stays in the database but is reachable over REST. An agent can call a stored procedure by name with its parameters and read the returned result set, triggering reporting or business logic without embedding SQL in the client.

Call a stored procedure by name with its input parameters and return the result set it produces.

Key Endpoints

4816 endpoints — the dreamfactory sql server api turns a microsoft sql server database into a rest interface, exposing each table for record reads and writes along with filtering, sorting, and pagination.

METHOD

PATH

DESCRIPTION

GET

Get the resources this service exposes

GET

/_table

Retrieve one or more tables

GET

/_schema

Retrieve table schema definitions

POST

/_schema

Create one or more tables

GET

/_proc

List stored procedures

POST

/_proc/{procedure_name}

Call a stored procedure by name

POST

/_func/{function_name}

Call a database function by name

GET

Get the resources this service exposes

GET

/_table

Retrieve one or more tables

GET

/_schema

Retrieve table schema definitions

POST

/_schema

Create one or more tables

GET

/_proc

List stored procedures

POST

/_proc/{procedure_name}

Call a stored procedure by name

POST

/_func/{function_name}

Call a database function by name

Why Jentic?

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

Setup

Wiring the DreamFactory SQL Server API by hand means choosing among its several auth schemes, learning its table, schema, procedure, and function URL conventions, and navigating thousands of generated endpoints. Through Jentic you install once, import the service from the API Directory, store the credential once, and your agent calls it.

Permission scoping

DreamFactory puts the table name in the URL path, so a rule can scope your agent to specific tables and to read-only record and schema operations. You choose the operations it may call, so destructive ones such as dropping a table or deleting records are not included unless you add them.

Credential isolation

Your DreamFactory 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 'query rows from a table' or 'call a stored procedure', and Jentic returns the matching DreamFactory operation with its input schema so the agent calls the right endpoint without scanning thousands of generated paths.

FAQs

Specific to using DreamFactory SQL Server API through Jentic.

What authentication does the DreamFactory SQL Server API use?

The spec declares several supported credentials: an API key sent as the X-DreamFactory-API-Key header or an api_key query parameter, a session token sent as the X-DreamFactory-Session-Token header or session_token query parameter, plus HTTP basic and bearer schemes. A request satisfies auth by presenting any one of them. Through Jentic the credential you use is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context.

Is there a DreamFactory MCP server?

You don't need an MCP server to give your agent the DreamFactory SQL Server API. Jentic connects it directly from the API Directory: import the service, store your credential once, and your agent calls its operations. Because this service exposes thousands of per-table endpoints, Jentic discovers the right operation on demand rather than loading every definition into the agent's context.

Can I limit what my agent is allowed to do with the DreamFactory SQL Server API?

Yes. Write a rule that allows only the read operations your agent needs, such as the table record reads and schema retrieval, so it can query data but cannot drop tables or write records, and every call it makes is logged. The table name travels in the URL path, so you can also scope a rule to the specific tables the agent should reach.

Can I call a stored procedure with the DreamFactory SQL Server API?

Yes. The procedure endpoints let you list the stored procedures the service exposes and call one by name with its parameters, returning the result set as JSON. The service exposes database functions the same way, so server-side logic stays in SQL Server but is reachable over REST.

What are the rate limits for the DreamFactory SQL Server API?

This OpenAPI spec does not specify rate limits; limits in a DreamFactory deployment are set per-role and per-service by the administrator who hosts it. Check your DreamFactory instance's role and limit configuration for the figures that apply to your API key.

How do I query a table with the DreamFactory SQL Server API through Jentic?

Install Jentic One, import the DreamFactory SQL Server service from the API Directory, and store your API key once. Your agent then searches by intent, for example 'query rows from a table', and Jentic returns the matching table endpoint with its filter and pagination parameters. To run it on your own infrastructure, install Jentic One from its GitHub repo.

DreamFactory SQL Server

AI ReadinessFoundational (D)47/100

See full scorecard

Community OpenAPI document · agent-readyStorageDatabaseapiKey, basic, bearer4816 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Read and write records in any SQL Server table over REST, retrieve and alter table schema, and call stored procedures and functions by name. DreamFactory auto-generates the endpoints from the database so an agent reaches the data over HTTP without a database driver.

Use for: Query rows from a SQL Server table, Insert new records into a table, Retrieve the schema definition for a table, Create a new table in the database

Not supported: Does not handle database hosting, backups, or user administration. Use for reading and writing SQL Server tables, schema, and stored procedures over REST only.

The DreamFactory SQL Server API turns a Microsoft SQL Server database into a REST interface, exposing each table for record reads and writes along with filtering, sorting, and pagination. It provides schema endpoints that retrieve, create, replace, and drop tables, and resource endpoints that list the tables, stored procedures, and functions the service makes available. Stored procedures and database functions are callable by name, so an application can run server-side database logic over HTTP without a direct database connection.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4

70%

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

100%

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.

50%

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

72%

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.

81%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

33%

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

64%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the DreamFactory SQL Server to your agent

Capabilities

Start building with DreamFactory SQL Server API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

DreamFactory SQL Server

Jentic AI Readiness Score

sqlsrv

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