Install Jentic One Beta

Connect the God Mode API to your agent

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

Rank nearby investors as buyers for a house by lat, lng, subject_asking_price, and subject_condition

Search for an investor by any LLC or person name it buys under and list its deals

Resolve a parcel from a point, an APN, or a street address and read its owner and deal history

Read the comparable sales, financing and liens, and building permits on a parcel

GET STARTED

Start building with God Mode API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use God Mode API for, with concrete tasks.

★ AI disposition agent matching buyers to a wholesale deal

A wholesaler's agent connected through Jentic searches by intent, finds the Investorlift buyer-match operation with its input schema, and calls it with the bearer key injected at execution time. Given the property's coordinates, asking price, and condition, it returns the investors who buy houses like this one with the reasons each fits, so the agent can draft outreach to the top buyers.

Call GET /v1/buyers/match with lat 33.476917, lng -111.920385, radius_miles 2, subject_asking_price 410000, and subject_condition MAJOR_REHAB, then return the top five investors with their fit reasons

Underwriting a parcel before making an offer

Before offering on a house, an investor needs the parcel's real numbers. The API resolves a parcel by address or APN, then returns its comparable sales within a chosen radius_miles, its dated financing, liens, and valuation, its building permits, and its listing cycles, all from public records.

Call GET /v1/properties/resolve with an address, then GET /v1/properties/{property_id}/comps and GET /v1/properties/{property_id}/financing for the returned parcel

Researching an investor or competitor

Investors often buy under many LLC names. The investor search finds a buyer by any name it uses, and the investor profile and deals operations show every purchase, flip, and holding grouped under one operator, plus the Investorlift wholesale listings that investor bought.

Call GET /v1/investors/search with q 'Desert Holdings LLC', then GET /v1/investors/{id}/deals for the top match and summarise purchase counts by kind

Lender market share for a ZIP or county

Brokers and lenders track who finances investor purchases. The lenders operations rank lenders by market, ZIP, city, county, or geometry with a hard_money filter, return each lender's loans and borrowers, and break a lender's activity down by month or area.

Call GET /v1/lenders with a zip and hard_money true, then GET /v1/lenders/{id}/borrowers for the top lender

Key Endpoints

39 endpoints — the investorlift god mode api reads county deed records for each loaded us market and returns real estate investor deals, the investors behind them, and a ranking of which investors best fit a given house.

METHOD

PATH

DESCRIPTION

GET

/v1/buyers/match

Rank investors as buyers for a property

GET

/v1/deals

List investor deals around a location

GET

/v1/investors/search

Find an investor by any name

GET

/v1/investors/{id}/deals

List one investor's deals

GET

/v1/properties/resolve

Resolve a parcel by point, APN, or address

GET

/v1/properties/{property_id}/comps

Comparable sales around a parcel

GET

/v1/lenders

Rank the lenders of a market

POST

/v1/properties/search

Search parcels by location and filters

GET

/v1/buyers/match

Rank investors as buyers for a property

GET

/v1/deals

List investor deals around a location

GET

/v1/investors/search

Find an investor by any name

GET

/v1/investors/{id}/deals

List one investor's deals

GET

/v1/properties/resolve

Resolve a parcel by point, APN, or address

GET

/v1/properties/{property_id}/comps

Comparable sales around a parcel

GET

/v1/lenders

Rank the lenders of a market

POST

/v1/properties/search

Search parcels by location and filters

Why Jentic?

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

Setup

Wiring Investorlift by hand means creating a zpka_ key, passing it as a bearer token, and learning cursor paging and the prefixed id conventions across deals, investors, parcels, and lenders. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.

Permission scoping

Investorlift puts investor, lender, and parcel ids in the URL path (/v1/investors/{id}, /v1/properties/{property_id}), so a rule can bound your agent to the operations it needs and to specific records where that fits. You choose the operations it may call, so broad pulls like lender loan books or parcel searches are not included unless you add them.

Credential isolation

Your Investorlift 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 buyers for a house' or 'get comps for a parcel', and Jentic returns the matching Investorlift operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using God Mode API through Jentic.

What authentication does the Investorlift God Mode API use?

Per its OpenAPI spec, every operation uses bearer authentication: an API key starting with zpka_, created in the Investorlift developer console, sent in the Authorization header. Through Jentic the key is stored by your own instance and attached to each call at execution time.

Can I find buyers for a specific house with this API?

Yes. GET /v1/buyers/match ranks nearby investors as buyers for a property. Pass lat and lng, a radius_miles, and the subject details such as subject_asking_price, subject_arv, subject_beds, subject_sqft, and subject_condition (for example LIGHT_REHAB or MAJOR_REHAB), and the response explains why each investor fits.

What are the rate limits for the Investorlift God Mode API?

The OpenAPI spec does not specify rate limits. Check the Investorlift developer documentation at https://developers.investorlift.com for current limits.

Is there an Investorlift MCP server?

You don't need an MCP server to give your agent Investorlift. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the deal, investor, and parcel operations it needs, discovered on demand rather than loaded into its context.

Can I limit what my agent is allowed to do with Investorlift?

Yes. For example, write a rule that allows only GET /v1/buyers/match and GET /v1/investors/{id}, so the agent can rank buyers for a deal and open their profiles but cannot pull lender loan books or run parcel searches, and every call it makes is logged.

How do I pull comps for a property through Jentic?

Import the Investorlift God Mode API from the Jentic API Directory and store your API key once. Your agent searches for 'comparable sales for a property', resolves the parcel with GET /v1/properties/resolve, then calls GET /v1/properties/{property_id}/comps with its schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Investorlift God Mode API

AI ReadinessAI-Ready (A-)77/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentCompany Databearer39 EndpointsREST

For Agents

Rank cash investors as buyers for a property, look up investor and lender profiles from county deed records, and read parcel comps, financing, and listings for AI agents.

Use for: I need buyers for a wholesale contract in Scottsdale, Find all LLCs that belong to the same investor, Get the comparable sales around this parcel, Check whether a property has liens or open financing

Not supported: Does not handle making offers, contract signing, or sending messages to investors. Use for reading investor, deal, parcel, listing, and lender data from public records only.

The Investorlift God Mode API reads county deed records for each loaded US market and returns real estate investor deals, the investors behind them, and a ranking of which investors best fit a given house. Investors are grouped so an operator's LLCs and the person behind them count as one buyer, and each investor profile lists every deal across the market. It also resolves parcels by point, APN, or street address and returns a parcel's owner, financing and liens, permits, comparable sales, and listing history, alongside MLS sale and rental listings, Investorlift wholesale listings, and lender rankings with their loans and borrowers.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

91%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

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: A+Signals: 4

70%

Description Coverage

Coverage of descriptions across API elements.

100%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

95%

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

71%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the God Mode API to your agent

Capabilities

Start building with God Mode API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Investorlift God Mode API

Jentic AI Readiness Score

God Mode 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