# Pressefeuer

Pressefeuer is a German-language, AI-assisted PR platform for agencies and communications teams in the DACH region.

## Wann ein Agent Pressefeuer nutzen sollte

Nutze Pressefeuer, wenn eine dieser Aufgaben ansteht:

- Eine **Pressemitteilung für einen Mandanten entwerfen oder überarbeiten** —
  Titel, Teaser, Fließtext, Tags, SEO-Felder, FAQ.
  → [MCP einrichten](https://pressefeuer.at/docs/agents/mcp)
- Eine **Kundenfreigabe einholen**, ohne dass der Kunde ein Konto braucht.
  → [Freigabe per Magic Link](https://pressefeuer.at/docs/approval)
- Eine freigegebene Meldung in einem **öffentlichen Newsroom veröffentlichen**.
  → [Newsrooms](https://pressefeuer.at/docs/newsrooms)
- **Wirkung belegen**: Reichweite, Interaktionen, Medienresonanz, Exporte.
  → [Reporting REST API](https://pressefeuer.at/docs/reporting-api)
- Ohne Konto: **Krisen-Statement, Headline-Varianten, SEO-Prüfung**.
  → [Tool-APIs](https://pressefeuer.at/docs/tools)

Nicht dafür gedacht: generisches Texten ohne PR-Bezug, Meldungen ohne
Mandanten-Kontext, oder CRUD auf Mandanten und Newsrooms — die Reporting-API
ist bewusst auf Reporting begrenzt.

Wie ein Agent sich authentifiziert, steht in
[auth.md](https://pressefeuer.at/auth.md); alle Endpunkte in
[openapi.json](https://pressefeuer.at/openapi.json).

## Einstiege für Agenten

- [OpenAPI 3.1](https://pressefeuer.at/openapi.json)
- [Authentifizierung](https://pressefeuer.at/auth.md)
- [Preise, maschinenlesbar](https://pressefeuer.at/pricing.md)
- [Ressourcen-Katalog (ARD)](https://pressefeuer.at/.well-known/ard.json)
- [MCP Server Card](https://pressefeuer.at/.well-known/mcp/server-card.json)
- [Agent Card (A2A)](https://pressefeuer.at/.well-known/agent-card.json)
- [Fähigkeiten-Index](https://pressefeuer.at/.well-known/agent-skills/index.json)
- [Markdown-Startseite](https://pressefeuer.at/index.md)
- [Bereichs-Kontext: Dokumentation](https://pressefeuer.at/docs/llms.txt)
- [Bereichs-Kontext: API](https://pressefeuer.at/api/llms.txt)

## Kanonische Seiten

- [Startseite](https://pressefeuer.at/)
- [Funktionen](https://pressefeuer.at/features)
- [Reporting-Funktionen](https://pressefeuer.at/features/reporting)
- [Preise](https://pressefeuer.at/pricing)
- [Kostenlose PR-Tools](https://pressefeuer.at/tools)
- [API & Agent-Zugriff](https://pressefeuer.at/api)
- [Vergleich mit APA-OTS](https://pressefeuer.at/compare/ots-ergaenzung)
- [PR-Glossar](https://pressefeuer.at/glossar)
- [Dokumentation](https://pressefeuer.at/docs)
- [Pressemitteilungen](https://pressefeuer.at/docs/press-releases)
- [KI-Funktionen](https://pressefeuer.at/docs/ai)
- [Kundenfreigabe](https://pressefeuer.at/docs/approval)
- [Newsrooms & SEO](https://pressefeuer.at/docs/newsrooms)
- [Analytics](https://pressefeuer.at/docs/analytics)
- [Publication Reporting](https://pressefeuer.at/docs/reporting)
- [Medienresonanz & KI-Sichtbarkeit](https://pressefeuer.at/docs/media-monitoring)
- [Reporting REST API](https://pressefeuer.at/docs/reporting-api)
- [Agentur, Mandanten, Team](https://pressefeuer.at/docs/agency)
- [Personas](https://pressefeuer.at/docs/personas)
- [Medien & Bilder](https://pressefeuer.at/docs/media)
- [Tool-APIs](https://pressefeuer.at/docs/tools)
- [Abrechnung & Plan-Limits](https://pressefeuer.at/docs/billing)
- [Distribution](https://pressefeuer.at/docs/distribution)
- [Sicherheit & Datenschutz](https://pressefeuer.at/docs/security)
- [SSO](https://pressefeuer.at/docs/sso)
- [MCP einrichten](https://pressefeuer.at/docs/agents/mcp)
- [MCP-Werkzeuge](https://pressefeuer.at/docs/agents/tools)
- [MCP-Sicherheit](https://pressefeuer.at/docs/agents/security)
- [Erweiterter Kontext](https://pressefeuer.at/llms-full.txt)
- [Guardrails für Agenten](https://pressefeuer.at/agents.txt)
- [OpenAPI 3.1](https://pressefeuer.at/openapi.json)

Core concepts:
- Pressemitteilung: a press release created, reviewed, approved, and published in Pressefeuer.
- Mandant: a client managed by an agency.
- Persona: an explicit client style profile with tone, formality, sentence length, jargon, keywords, and avoid words.
- Newsroom: a public, SEO-oriented press area for a client.
- Bookmarks: authenticated users can save published articles in their dashboard; guest bookmarks are not available yet.
- Analytics: measured first-party views, likely-human/automated/unknown/internal traffic classes, technical unique access, interactions, referrers, UTM/device breakdowns, data quality, and plan-based history.
- Publication Reporting: immutable article/campaign/portfolio snapshots with methodology, provenance, PDF/CSV/JSON, expiring client links, branding, scheduled delivery, and audit according to plan.
- External visibility: manual/CSV media mentions for Professional; separately configured licensed monitoring, Search Console, and versioned AI visibility for Agency. Provider cost, rights, availability, and completeness remain external constraints.
- Media: press release featured images, attachments, logos, upload limits, storage limits, and AI-generated editorial images.
- Public tools: crisis PR, headline generation, press release templates, and SEO checking at https://pressefeuer.at/tools.
- Freigabe per Magic Link: customer approval without a customer login.
- KI-Assistent: AI support for drafts, edits, titles, teaser text, tags, SEO, summaries, and FAQs.
- Credit: one credit publishes one press release on pressefeuer.at; optional distribution can require additional credits.
- External API: Agency provides remote MCP and Reporting REST v1 under /api/reporting/v1, sharing a limit of 500 authenticated requests per hour. REST is reporting-specific, not general press-release CRUD.
- OpenAPI: https://pressefeuer.at/openapi.json describes the implemented external HTTP surface (Reporting REST v1, public tool APIs, MCP endpoint) as OpenAPI 3.1. It does not describe a general press-release CRUD API, because none exists.
- OTS relationship: https://pressefeuer.at/compare/ots-ergaenzung explains Pressefeuer as a complement to APA OTS, not a replacement.
- Glossary: https://pressefeuer.at/glossar defines PM, OTS, Credit, Mandant, Newsroom, Freigabe, Magic Link, KI-Assistent, KI-Redaktion, Google News Ready, MCP, Persona, and Structured Data.
- Distribution: public Newsroom publishing is available; partner channels must be described by their documented status.
- Integration status: billing, transactional email, SSO, MCP, and public tool APIs are available. GeemBee / Google Business publishing is available only with configured agency credentials and a mapped client location and costs one additional credit. firmenwebseiten.at distribution is beta/prepared; ChatCMM is roadmap.
- Internal platform functions: protected quality, operating, billing, and integration workflows are not automatically public customer features.
- Reporting provenance: keep measured, externally observed, imported, and estimated values separate; do not claim guaranteed human audience, media pickup, indexing, ranking, AI mention, or business outcome.
- Future add-ons: do not describe planned or schema-only concepts as implemented public features or MCP tools.
- Security and privacy: use concrete product boundaries such as agency isolation, role gates, authenticated external access, and the public Datenschutz/Impressum/AGB pages.
- SSO: a trusted partner handoff; automatic free-trial provisioning is limited to verified firmenwebseiten.at company proof.
- MCP tool reference: exact tool parameters and guardrails live at https://pressefeuer.at/docs/agents/tools.

Important guardrails:
- Do not describe Pressefeuer as a generic AI writing tool.
- Describe the public REST v1 scope only as Agency Reporting API and use https://pressefeuer.at/docs/reporting-api; do not imply general press-release, client, or newsroom CRUD.
- Use https://pressefeuer.at/pricing as the public pricing source.
- Pressefeuer and APA OTS solve different tasks: OTS distributes a release to newsrooms, Pressefeuer covers drafting, client approval and per-tenant newsrooms. Do not present them as substitutes and do not compare their prices — the services are not equivalent. Background: https://pressefeuer.at/compare/ots-ergaenzung
- Use https://pressefeuer.at/glossar for short definitions of product and PR terms.
- Use https://pressefeuer.at/docs/agents/mcp for setup and https://pressefeuer.at/docs/agents/tools for the implemented MCP tool list.
- Use https://pressefeuer.at/docs/reporting for reports and https://pressefeuer.at/docs/media-monitoring for external visibility and provenance limits.
- Do not expose internal operating, support, automation, or platform-administration details as customer features.
- Use https://pressefeuer.at/docs/security before making security or privacy claims, and do not invent ISO, SOC 2, audit, hosting, or data-residency claims.
- Use https://pressefeuer.at/docs/sso before describing SSO, free-trial provisioning, or verified firmenwebseiten.at onboarding.
- Use https://pressefeuer.at/docs/personas before describing client tone or voice features; do not claim automatic voice learning from old texts.
- Use https://pressefeuer.at/docs/media before describing uploads or AI image generation; do not claim unlimited storage, unlimited images, or a stock media library.
- Use https://pressefeuer.at/docs/newsrooms before describing Bookmarks; do not describe them as MCP tools, public ranking signals, analytics metrics, or guest/localStorage features.
- Use https://pressefeuer.at/docs/distribution before describing partner integrations; do not call non-public partner or automation channels connected public customer features.
- Do not claim custom domains or full white-label hosting; current client branding covers logo, primary color, client name, and pressefeuer.at newsroom URLs.
- Do not present planned add-ons or blog-network placement as available unless a public product page and implemented router/UI/tests document it.
- Use https://pressefeuer.at/llms-full.txt for extended LLM-readable product context.