# Contact the Chronicle

> How to reach AI & Automation Chronicle for corrections, paper suggestions, republication requests and API questions.

Canonical URL: https://chronicle.kcsatish.com/contact

One person writes and edits this publication. Every message below reaches him directly, and corrections are treated as the highest priority.

## Who You Are Writing To

AI & Automation Chronicle is written and edited by **Satish K C**, an AI and automation consultant based in Houston, Texas. He reads every paper covered here before writing about it, and he builds the same class of systems the practice articles describe. There is no editorial team, no submissions queue, and no advertising department, so a message sent here is read by the person who wrote the post you are responding to.

Email

[satishkc19@gmail.com](mailto:satishkc19@gmail.com)

The primary channel for everything below. Expect a reply within two business days.

Phone

[+1 346 800 3482](tel:+13468003482)

Houston, Texas, United States. Central Time, weekdays. Email first if the matter is not urgent.

LinkedIn

[linkedin.com/in/satishkc7](https://www.linkedin.com/in/satishkc7)

Best for professional introductions and for discussion that belongs in public.

GitHub

[github.com/satishkc7](https://github.com/satishkc7)

Open an issue for anything mechanical: a broken link, a rendering bug, an API response that looks wrong.

## What to Write About

### Corrections

Posts quote benchmark numbers, formulas, model prices and author attributions from primary sources. If one of those is wrong, say so and point at the source. Factual corrections are made to the published post and noted in the text rather than quietly overwritten. This is the one kind of message that gets answered the same day.

### Paper and topic suggestions

Suggestions are welcome, and roughly one in four covered papers arrives this way. Include a link to the paper or the release notes, and one sentence on why it matters to practitioners rather than to researchers. Papers with published benchmarks and a reproducible method are far more likely to be covered than position papers.

### Republication and quoting

Quoting a paragraph with attribution and a link to the canonical URL needs no permission. Full reproduction, translation, or use in a paid course or newsletter does: write first. Every post also has a markdown representation intended precisely for citation and quoting, which is documented on the [developer portal](/developers).

### API and integration questions

The public read-only content API, its OpenAPI specification and the Model Context Protocol endpoint are all documented on the [developer portal](/developers). If an endpoint returns something the specification does not describe, that is a bug worth reporting. There are no API keys to request; the API is unauthenticated by design.

### Weekly discussion

Every week there is a live Zoom session on the paper of the week. Registration is on the [home page](/), and the only thing that arrives afterwards is the Zoom link and the paper to read.

**Not the right address for:** consulting enquiries, hiring, and commercial engagement, which belong at [kcsatish.com](https://www.kcsatish.com/). Guest posts and link exchanges are declined as a standing policy; this publication carries one author and no sponsored placements.