[REQUEST] Arcmira: YouTube Transcript Search integration

Abierto
  • ¿Algo no está bien?
#8,607 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend-api-design

Línea de trabajo

Read the contribution guide for staging and inspect the tool, block, icon, and generated catalog registration requirements first. Use the linked OpenAPI contract and search, authentication, and usage documentation to define the two actions, credential handling, outputs, and error behavior. Done means maintainers agree on the native two-action scope and the required registrations are updated.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Is your feature request related to a problem? Please describe.

This is a first-party proposal from Arcmira. Sim users can connect Arcmira through the generic MCP or API blocks, but there is no native Arcmira block in the current staging registry. A native block could make timestamped YouTube transcript research available through named actions and documented outputs, without hand-authoring HTTP requests or MCP programs.

Describe the solution you'd like

Add an Arcmira integration, displayed as Arcmira: YouTube Transcript Search where the catalog permits descriptive titles, with two initial actions:

  • Resolve a person, channel or company name through GET /v1/entities/resolve. Return the resolution options instead of silently choosing an ambiguous name.
  • Search spoken transcript passages through GET /v1/search, with a user-controlled result limit and optional documented filters. Preserve timestamped source links, speaker information when available, coverage, partial results and access restrictions.

Use the user's account API key as a user-only configuration input, never a model-supplied argument. Pass credentials in the bearer header. Errors should preserve the API status/code and documentation link, including quota, access and rate-limit failures. The initial block covers entity resolution and indexed search. If expanded to Premium transcript retrieval, paid reads use credits from your plan, then your on-demand budget.

API docs: https://arcmira.com/docs

OpenAPI contract: https://api.arcmira.com/v1/openapi.json

Search guide: https://arcmira.com/docs/search

Authentication and usage: https://arcmira.com/docs/authentication and https://arcmira.com/docs/usage-and-billing

Describe alternatives you've considered

  • Existing remote MCP connection: https://mcp.arcmira.com/mcp. It provides broader research and account operations, with its own tool-effect and entitlement rules: https://arcmira.com/docs/mcp-server
  • Generic API block against https://api.arcmira.com/v1 with the user's bearer key.
  • Separate keyless API-documentation MCP at https://arcmira.com/docs/mcp for developers building integrations. This searches documentation, not video transcripts.

Additional context

Would maintainers prefer a native two-action block or a maintained MCP workflow example? The contribution guide targets staging and requires the tool, block, icon and generated catalog registrations. This proposal seeks agreement on the contribution scope. The local search-and-entity-resolution candidate passed the full repository test suite, repository audits and all-workspace typechecking on October 16, 2026. Both actions also succeeded through the native HTTP routes using an isolated read-only test account, with unchanged account usage. These are dated local results; the candidate still needs a refresh against current staging before contribution. The candidate has not been submitted as a PR or accepted by Sim. Free account API access is available within account allowances, with plan-dependent features and freshness. No credentials or private data are included.

Lenguaje dominante
TypeScript
Estrellas
29.8k
Forks
3.9k
Merge medio
1 h 44 min
PR fusionados (30 d)
841

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de simstudioai/sim

Todos los issues de simstudioai/sim

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.