# md.tasta.space/agent

Upload a markdown file and get a link to a clean reading page. Links last 88 min to 69 h. 1 upload per 10 minutes per IP, up to 5 MB.

## Upload

Send the file body as raw markdown:

```bash
curl -X POST https://md.tasta.space/agent \
  -H "Content-Type: text/markdown" \
  -H "X-Filename: notes.md" \
  --data-binary @path/to/notes.md
```

Or as a multipart form:

```bash
curl -X POST https://md.tasta.space/agent -F "file=@path/to/notes.md"
```

| Option | What it does | Default |
| --- | --- | --- |
| `X-Filename` or `?filename=` | Name shown on the page | `agent-upload.md` |
| `?lifetime=` | How long the link lives: `88m`, `420m`, `1337m` or `69h` | `69h` |
| `Accept: application/json` | JSON reply with `slug`, `share_url`, `delete_key`, `expires_at` | plain text |

`?lifetime=` also takes plain minutes (88, 420, 1337, 4140). Older calls with `?expiry=1`, `2` or `3` (days) still work and get the nearest lifetime, never more than 69 h.

The reply is the share URL on one line. Give it to the user, and mention that it expires: they should download the file if they want to keep it.

## Formatting: make it easy to read

Everything below renders on the page. Use every feature that fits the content, so the document is easy to scan.

### Title and sections

Always. Start with one `#` title and a one-line summary. Every `##` becomes an entry in the contents sidebar and the label in the reading bar, so keep section names short.

````markdown
# Release 2.4
What changed, and what to do before Friday.

## Breaking changes
### Auth tokens
````

### Alerts

For what the reader must not miss: warnings, risks, decisions, tips. Types are NOTE, TIP, IMPORTANT, WARNING and CAUTION. A few per document, not one per paragraph.

````markdown
> [!WARNING]
> Run the migration before you deploy.

> [!TIP]
> `--dry-run` shows the plan first.
````

### Code

Always fence code and always name the language. It gets highlighting and a copy button.

````markdown
```bash
php artisan migrate --force
```
````

### Diagrams

For anything with a shape: flows, architecture, layers, timelines. Draw it with box-drawing characters in a plain fence; the lines join up on the page.

````markdown
```
┌─────────┐     ┌─────────┐
│ request │ ──▶ │ handler │
└─────────┘     └────┬────┘
                     ▼
                ┌─────────┐
                │  queue  │
                └─────────┘
```
````

### Tables

For comparisons, options and numbers. Number columns line up on the right by themselves, and wide tables scroll with the first column pinned.

````markdown
| Plan | Price | Seats |
| --- | --- | --- |
| Solo | €9 | 1 |
| Team | €29 | 10 |
````

### Task lists

For plans, follow-ups and anything the reader has to do.

````markdown
- [x] Write the migration
- [ ] Backfill old rows
- [ ] Remove the flag
````

### Footnotes

For sources and asides that would break the flow of a sentence.

````markdown
Cold starts dropped by 40%.[^bench]

[^bench]: Median of 20 runs on a CX22.
````

### Definitions

For glossaries and terms the reader may not know.

````markdown
Idempotent
: Safe to run twice. The second run changes nothing.
````

### Collapsible sections

For long material most readers can skip: full logs, big configs, raw output.

````markdown
<details>
<summary>Full error log</summary>

SQLSTATE[23000]: duplicate entry

</details>
````

### Keys and inline marks

For shortcuts and the odd highlight. Only these HTML tags work: details, summary, kbd, mark, sub, sup, ins, br. Any other HTML is removed, and so are attributes.

````markdown
Press <kbd>Cmd</kbd> + <kbd>K</kbd>, then <mark>Deploy</mark>.

H<sub>2</sub>O, E = mc<sup>2</sup>, ~~old~~ <ins>new</ins>
````

## Before you upload, check

1. A `#` title and a one-line summary at the top.
2. Content split into `##` sections with short names.
3. Steps as numbered lists, comparisons as tables.
4. Every code block fenced, with its language.
5. Warnings, risks and key decisions in alerts.
6. Anything with a shape (flow, architecture, timeline) drawn as a diagram.
7. Long side material (full logs, big configs) folded into `<details>`.