canonical: https://jentic.com/apis/techy-api.vercel.app/techy-api-vercel

# Techy API

A simple API that generates cool tech-savvy sounding phrases. Returns random techy phrases in either plaintext or JSON format. The API exposes 2 endpoints.

## For AI agents

Programmatically get a random techy phrase in plaintext, get a random techy phrase in json format. Covers 2 operations.

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- Get a random techy phrase in plaintext
- Manage hr recruiting data programmatically
- Integrate Techy API into automated workflows
- Query and filter Techy API records by parameters
- Monitor Techy API operational status and events

## Use cases

### HR and Recruiting Operations

Use the Techy API to perform hr recruiting operations programmatically. The API provides 2 endpoints covering core functionality including get a random techy phrase in plaintext, get a random techy phrase in json format.

Example prompt: Call GET `/api/text` to get a random techy phrase in plaintext

### Data Retrieval and Monitoring

Query Techy API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Techy API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Techy API 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 none tokens manually.

Example prompt: Search Jentic for 'get a random techy phrase in plaintext', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/text` | Get a random techy phrase in plaintext |
| GET | `/api/json` | Get a random techy phrase in JSON format |

## Key resources

- **Json** — Operations for json
- **Text** — Operations for text

## 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:** 72 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 73 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/techy-api.vercel.app/techy-api-vercel/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 the Techy API by hand still means writing the HTTP client, response parsing, and retry handling for its text and JSON endpoints yourself, even though it needs no credential. Through Jentic you install once, import the Techy API from the API Directory, and your agent calls it with no key to manage.
- **Permission scoping:** The Techy API exposes only read endpoints, so limit the agent to the operations it needs, such as fetching text or JSON output. You choose that allowed set, and only the read operations you name are available to the agent.
- **Credential handling:** The Techy API needs no credential, so there is nothing for your Jentic One instance to store. No secret ever enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get a random tech phrase as text' or 'get it as JSON', and Jentic returns the matching Techy API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### What authentication does the Techy API use?

The Techy API uses no authentication. 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 get a random techy phrase in plaintext with the Techy API?

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

### What are the rate limits for the Techy API?

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 get a random techy phrase in plaintext through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get a random techy phrase in plaintext'. Jentic returns the matching Techy API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Techy API have?

The Techy API exposes 2 endpoints covering json, text operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Techy API operations the agent may call, and the Techy API exposes only read endpoints. You can allow just GET `/api/text` for plaintext phrases, just GET `/api/json` for JSON output, or both, and any operation you do not name stays unavailable to the agent. Since this API needs no credential, there is nothing extra to store, and the agent can only reach the read operations you have granted.