canonical: https://jentic.com/apis/searchify.com/searchify

# Searchify Search

Searchify is a hosted search API that provides real-time full-text search and autocomplete capabilities for web applications. The API exposes 14 endpoints secured with basic authentication.

## For AI agents

Programmatically list all indexes, get index metadata. Covers 14 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- List all indexes
- Get index metadata
- Create or update an index
- Delete an index
- Add or update documents in an index
- Update scoring variables for a document

## Use cases

### Developer Tools Operations

Use the Searchify Search to perform developer tools operations programmatically. The API provides 14 endpoints covering core functionality including list all indexes, get index metadata, create or update an index.

Example prompt: Call GET /indexes to list all indexes

### Automated Indexes Management

Automate indexes operations by combining multiple Searchify Search endpoints. Agents can get index metadata and then create or update an index in a single workflow.

Example prompt: Call GET `/indexes/{name}` to get index metadata, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Searchify Search endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Example prompt: Search Jentic for 'list all indexes', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/indexes` | List all indexes |
| GET | `/indexes/{name}` | Get index metadata |
| PUT | `/indexes/{name}` | Create or update an index |
| DELETE | `/indexes/{name}` | Delete an index |
| PUT | `/indexes/{name}/docs` | Add or update documents in an index |
| DELETE | `/indexes/{name}/docs` | Delete documents from an index |
| PUT | `/indexes/{name}/docs/variables` | Update scoring variables for a document |
| PUT | `/indexes/{name}/docs/categories` | Update categories for a document |

## Key resources

- **Indexes** — Operations for indexes

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 39 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 50 / 100
- **View full report:** https://jentic.com/apis/searchify.com/searchify/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Searchify Search by hand means setting up its basic auth, resolving the per-account {privateUrl} subdomain into the right host, and managing index and document calls yourself. Through Jentic you install once, import Searchify Search from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Searchify puts the index name in the URL path (`/indexes/{name}/...`), so a rule can pin your agent to one index: it can add and update documents there and nothing else. You choose the operations it may call, so destructive ones like deleting an index or clearing its documents are not included unless you add them.
- **Credential handling:** Your Searchify basic credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'add documents to an index' or 'list all indexes', and Jentic returns the matching Searchify operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Searchify Search use?

The Searchify Search uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list all indexes with the Searchify Search?

Yes. Use the GET /indexes endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Searchify Search?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list all indexes through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list all indexes'. Jentic returns the matching Searchify Search operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Searchify Search have?

The Searchify Search exposes 14 endpoints covering indexes operations.

### Can I limit what my agent is allowed to do with the Searchify Search API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Searchify operations and credentials the agent may use. Because Searchify puts the index name in the URL path (`/indexes/{name}/...`), you can pin the agent to a single index and let it add or update documents there and nothing else. You choose the operations it may call, so destructive ones like deleting an index (DELETE `/indexes/{name}`) or clearing its documents (DELETE `/indexes/{name}/docs`) stay out of reach unless you add them.