> ## Documentation Index > Fetch the complete documentation index at: https://www.usenotra.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Run a GEO persona now > Plays the persona's conversation now and uses AI credits at twice the rate of a single prompt check. API-based answer engines run synchronously, so the request can stay open for several minutes; `checks`, `mentions` and `engines` report their result. Tracked consumer apps are queued as a background scan named by `queuedScanId`; poll `GET /v1/projects/{projectId}/geo/scans/{scanId}` for that part. Use a client timeout of at least five minutes. After four minutes the API answers 409 while the run finishes on its own; do not retry, read `GET …/personas/{personaId}/results` instead. ## OpenAPI ````yaml https://api.usenotra.com/openapi.json post /v1/projects/{projectId}/geo/personas/{personaId}/run openapi: 3.1.1 info: title: Notra API version: 1.0.0 description: >- OpenAPI schema for Notra content endpoints. Use GET /v1/status for public reachability. Error responses include recovery guidance. Breaking changes ship under a new major path; deprecated operations send Deprecation and Sunset headers at least 90 days before removal. servers: - url: https://api.usenotra.com description: Production - url: https://demo-api.usenotra.com description: >- Sandbox with sample data. Get a free sandbox key at demo.usenotra.com, no signup needed security: - BearerAuth: [] tags: - name: Webhooks description: Manage outbound webhook subscriptions and delivery history. - name: Discovery description: Public API status and authenticated workspace discovery. - name: Content description: >- Manage posts, brand identities, and GitHub or Linear integrations, and queue content generation. Organization is inferred from the API key (identity.externalId). - name: Schedules description: >- Manage scheduled content generation. Organization is inferred from the API key (identity.externalId). - name: Event Triggers description: >- Manage event-based content generation triggered by GitHub webhooks. Organization is inferred from the API key (identity.externalId). - name: Chats description: >- Manage chat sessions. Organization is inferred from the API key (identity.externalId). - name: Skills description: >- Manage reusable writing skills. Organization is inferred from the API key (identity.externalId). - name: Feedback description: >- Collect and triage feedback submitted by AI agents. Agents post to the organization's feedback URL without credentials; reading and triage require an API key with feedback.read or feedback.write. - name: GEO description: >- Manage generative engine optimization: projects, tracking settings, prompts, prompt sequences, competitors, scans, visibility reads, content gaps and briefs, agent readiness and AI traffic. Project-scoped endpoints require the GEO plan entitlement in addition to their scope; organization-level ingest endpoints require only the traffic scope. - name: Sites description: >- Notra Sites are hosted blogs and changelogs built from a GitHub repository. Read Sites and their deployments, start builds, preview posts on a Site, open pull requests that publish posts to it, and manage blog.json authors and the author page through staged Design changes. Domains, settings, rollbacks and deletion stay in the dashboard. externalDocs: description: Notra API versioning and deprecation policy url: https://www.usenotra.com/docs/api/versioning paths: /v1/projects/{projectId}/geo/personas/{personaId}/run: post: tags: - GEO summary: Run a GEO persona now description: >- Plays the persona's conversation now and uses AI credits at twice the rate of a single prompt check. API-based answer engines run synchronously, so the request can stay open for several minutes; `checks`, `mentions` and `engines` report their result. Tracked consumer apps are queued as a background scan named by `queuedScanId`; poll `GET /v1/projects/{projectId}/geo/scans/{scanId}` for that part. Use a client timeout of at least five minutes. After four minutes the API answers 409 while the run finishes on its own; do not retry, read `GET …/personas/{personaId}/results` instead. operationId: runGeoPersona parameters: - schema: type: string minLength: 1 pattern: ^[A-Za-z0-9_-]{1,100}$ example: b1f2c3d4-0000-4000-8000-000000000000 required: true name: projectId in: path - schema: type: string minLength: 1 pattern: ^[A-Za-z0-9_-]{1,100}$ required: true name: personaId in: path responses: '200': description: >- API-based engines finished; a queued consumer-app scan is named by queuedScanId content: application/json: schema: $ref: '#/components/schemas/RunGeoPersonaResponse' '400': description: Invalid request content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Missing or invalid API key content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '402': description: GEO plan or available AI credits required content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: Forbidden content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: Organization, project or resource not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '409': description: >- Persona run is still running after the internal timeout; do not retry the run content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '429': description: >- Rate limit exceeded. This endpoint allows 10 requests per 10 minutes per organization. headers: RateLimit-Limit: description: Maximum requests allowed in the current window. schema: type: integer RateLimit-Remaining: description: Requests remaining in the current window. schema: type: integer RateLimit-Reset: description: Seconds until the current window resets. schema: type: integer Retry-After: description: Seconds the client should wait before retrying. schema: type: integer content: application/json: schema: $ref: '#/components/schemas/RateLimitErrorResponse' '500': description: Internal server error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '503': description: Authentication or billing service unavailable content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: schemas: RunGeoPersonaResponse: type: object properties: checks: type: integer description: >- Answers recorded during this request by the API-based engines that responded. mentions: type: integer engines: type: array items: type: string queuedScanId: type: - string - 'null' default: null description: >- Scan that plays the persona in the tracked consumer apps in the background, or `null`. Poll `GET /v1/projects/{projectId}/geo/scans/{scanId}`. queuedEngines: type: array items: type: string default: [] organization: type: object properties: id: type: string slug: type: string name: type: string logo: type: - string - 'null' required: - id - slug - name - logo required: - checks - mentions - engines - organization ErrorResponse: type: object properties: error: type: string code: type: string recovery: type: string required: - error RateLimitErrorResponse: type: object properties: error: type: string limit: type: integer minimum: 1 remaining: type: integer minimum: 0 reset: type: integer required: - error - limit - remaining - reset securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: API Key description: >- Send your API key in the Authorization header as Bearer API_KEY. Account API keys work in every workspace you belong to: send X-Notra-Organization-Id with the workspace id or slug to choose one. Workspace endpoints require it when you belong to more than one workspace; GET /v1/me/workspaces works without it. Organization keys only accept their own workspace there. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.