canonical: https://jentic.com/apis/getosh.today/getosh

# Getosh Today Getosh API

The Getosh API tracks tasks and attaches the work done against them. It searches the task list, updates a task with scraped data once a worker has processed it, appends log entries to a task to record progress, and attaches files to a task such as screenshots or exported results. The task is the unit of work that ties a request to its logs and outputs, so an automation can claim a task, record what it found, and hand back artifacts. It is aimed at scraping and worker pipelines that coordinate units of work through a shared task queue.

## For AI agents

Coordinate work through tasks: search the task list, update a task with scraped data, append log entries, and attach files such as screenshots or exported results.

## Scope

Does not handle scheduling, billing, or user management. Use for retrieving and updating scraper tasks with logs and files only.

## Capabilities

- Search the task list to find work to pick up
- Update a task with scraped data once a worker has processed it
- Append log entries to a task to record progress
- Attach files to a task such as screenshots or exported results
- Tie logs and output files to the task that produced them

## Use cases

### Agent-driven task worker

An AI agent acting as a worker can call the Getosh API through Jentic to search for a task to process, update it with the scraped data once done, and attach any output files. Jentic returns the task operations from a natural-language query, so the agent drives the queue without reading the Getosh reference first.

Example prompt: Search for an available task, update it with the scraped data once processed, and attach the result file to the same task.

### Progress logging on a task

Append log entries to a task as a worker makes progress so an operator can follow what happened without re-running the job. The log operation records each step against the task, giving a timeline from pickup to completion.

Example prompt: Add a log entry to the task recording the step just completed, then confirm the entry is attached to that task.

### Artifact attachment

Attach files such as screenshots or exported data to the task that produced them, keeping the output alongside the record of the work. Pipelines use this so every task carries its evidence rather than storing artifacts in a separate system.

Example prompt: Attach the exported result file to the completed task and confirm it is linked to that task.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/tasks` | Search tasks |
| PUT | `/tasks/{id}` | Update a task with scraped data |
| POST | `/tasks/{id}/log` | Add a log entry to a task |
| POST | `/tasks/{id}/files` | Attach a file to a task |

## Key resources

- **Tasks** — Search tasks, update a task with scraped data, append log entries, and attach files

## 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:** 48 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 75 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 13 / 100
- **View full report:** https://jentic.com/apis/getosh.today/getosh/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 Getosh API by hand means handling its bearer token and coding the task search, update, log, and file calls yourself. Through Jentic you install once, import the API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Getosh puts the task id in the URL path, so a rule can pin your agent to one task and the operations you pick, such as searching and appending logs. You choose which operations it may call, so the update and file operations are not included unless you add them.
- **Credential handling:** Your Getosh token 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 'update a scraper task' or 'attach a file to a task', and Jentic returns the matching Getosh operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Asana API** — Task and project tracking for teams
- **ClickUp API** — Task management with custom fields and statuses
- **monday.com API** — Work-management boards and item tracking

## FAQ

### Is there a Getosh API MCP server?

You do not need an MCP server to give your agent the Getosh API. Jentic connects it directly from the API Directory: import the API, store your token once, and your agent calls the task search, update, log, and file operations. Operations are discovered on demand, so no extra server definitions load into the agent's context.

### What authentication does the Getosh API use?

The API authenticates with a bearer token per its OpenAPI spec, sent in the Authorization header on every task call. Through Jentic the token is stored encrypted in your own Jentic One instance and supplied only when an allowed call runs, so it never reaches the agent's context.

### Can I attach files to a task with the Getosh API?

Yes. The file operation attaches a file such as a screenshot or exported result to a specific task by its id, and a separate log operation appends progress entries to the same task. Both keep the output tied to the task that produced it.

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

The OpenAPI spec does not specify rate limits. The surface is small and worker-oriented, so confirm the request limits that apply to your account in the Getosh documentation at https://app.getosh.today.

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

Yes. Getosh puts the task id in the URL path, so a rule can scope the agent to one task and the operations you pick, such as searching and appending logs, while leaving the update and file operations out of the allowed set, with every call logged.

### How do I update a task with the Getosh API through Jentic?

Search Jentic for 'update a scraper task' to surface the task update operation, load its input schema, pass the task id and scraped data, and execute, then attach any result file. To run it on your own infrastructure, install Jentic One from its GitHub repo.