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

# Arison8 Smolabot Trade Economics Check

The Smolabot Trade Economics Check API answers one question with arithmetic: does a proposed long trade still clear after fees, spread, slippage, and an optional profit buffer? It makes no predictions, pulls no market data, and places no orders. The check costs one prepaid credit on success and nothing on failure, and a health endpoint returns service info and the fixed calculation model version so the same inputs always produce the same output.

## For AI agents

Run deterministic trade-economics arithmetic: given a proposed long trade's fees, spread, slippage, and an optional profit buffer, return whether it clears. A health endpoint reports service info and the model version. Authenticate the check with a bearer key.

## Scope

Does not place orders, provide market data, or predict prices. Use for post-cost long-trade clearance arithmetic only.

## Capabilities

- Check whether a proposed long trade clears after fees, spread, and slippage
- Factor an optional profit buffer into the clearance calculation
- Read service info and the fixed calculation model version from the health endpoint

## Use cases

### Pre-Trade Cost Screening

Before an agent acts on a trade idea, it sends the proposed long trade's fees, spread, slippage, and profit buffer to Smolabot and receives a clear yes or no on whether the position clears. Because the model is deterministic and version-pinned, the same inputs always return the same answer, so the agent gets a stable cost gate rather than a prediction.

Example prompt: Call POST /check with the trade's fees, spread, slippage, and profit buffer, then act only if it reports the trade clears

### Strategy Rule Gate

An agent running a trading strategy calls Smolabot as a final arithmetic gate on each candidate long trade, filtering out any that do not clear after costs. Each successful check costs one prepaid credit and failures cost nothing, so the agent can screen many candidates while only paying for the checks that return a result.

Example prompt: Call POST /check for each candidate long trade and keep only the ones the response reports as clearing after costs

### AI Agent Integration via Jentic

An AI agent reaches the Smolabot check through Jentic without holding the bearer key itself. It searches by intent, receives the check operation with its input schema, and executes the call with the credential injected at run time, so the trade-economics gate drops into a larger trading or analysis workflow.

Example prompt: Search Jentic for 'check whether a trade clears after fees', load the POST /check schema, and execute it with Jentic-managed credentials

## Key resources

- **Trade Check** — Run the deterministic long-trade clearance calculation via POST /check
- **Service** — Read service info and the calculation model version via GET /health

## 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:** 57 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 33 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/arison8.com/arison8/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 Smolabot by hand means managing its smk_ bearer key, tracking your prepaid credit balance, and reading the model version yourself. Through Jentic you install once, import Smolabot from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Smolabot carries the trade figures inside the request body, so a rule bounds which operations your agent may call. The API offers only the check and the open health read, so you can allow the clearance check and nothing that could reach any other surface.
- **Credential handling:** Your Smolabot 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.
- **Discovery method:** Agents search Jentic by intent such as 'check whether a trade clears after fees', and Jentic returns the Smolabot check operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Polygon.io** — Market data for prices, quotes, and reference data
- **Alpha Vantage** — Stock, forex, and crypto market data and indicators
- **Finnhub** — Real-time market data and financial fundamentals

## FAQ

### What authentication does the Smolabot Trade Economics Check API use?

The check authenticates with a bearer key in the Authorization header, per its OpenAPI spec, with keys shaped like smk_ for your account. The health endpoint is open and needs no credential. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.

### Can I check whether a trade clears after costs with the Smolabot API?

Yes. POST /check takes a proposed long trade's fees, spread, slippage, and an optional profit buffer and returns whether it clears, using arithmetic only with no market data or predictions. The model is version-pinned, so the same inputs always return the same answer.

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

Smolabot charges one prepaid credit per successful check and nothing on failure rather than enforcing a fixed rate ceiling, and the OpenAPI spec does not state request limits. Watch for HTTP 429 responses and check Smolabot's documentation for the current limits before running large batches.

### How do I check whether a trade clears with the Smolabot API through Jentic?

Search Jentic for 'check whether a trade clears after fees', and it returns the Smolabot operation with its input schema. Load the schema and execute POST /check with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a Smolabot MCP server?

Yes, Smolabot offers an MCP server for its check. You can also connect it directly through Jentic: your agent gets the full 2-endpoint surface without loading another server's tool definitions into its context, your credential is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.

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

Yes. The API has only the check and health operations, so a rule can allow the agent to run the clearance check and read service info and nothing else. The check never places an order or moves money, and every call runs through your own instance where it is logged for review.