Arcmira: YouTube Transcript Search for Langflow
Arcmira · API documentation · API schema
An opt-in Python extension with two native Langflow components:
- YouTube Transcript Search: find timestamped passages, retaining source links, coverage and access metadata.
- Entity Resolve: resolve names and handles without silently choosing among ambiguous candidates.
A paid read uses credits from your plan, then your on-demand budget. The configured budget is the approval. API plan limits and refusals remain visible. Selecting Premium never triggers a caption fallback. This extension makes one API request per component execution; it does not retry automatically.
Local installation
This extension is installed separately from Langflow. With a compatible Langflow/LFX installation, install it in the same environment:
python -m pip install lfx-arcmira==0.1.0
lfx extension list
It registers through the official langflow.extensions entry point. Restart Langflow after installation. Add an Arcmira API key to the component's secret field. Search by IDs after resolving names; inspect candidates and clarification before choosing an entity. The query input supports native tool mode. No model is required to call a component's output directly.
Both components return the complete API JSON envelope in Data. A non-success HTTP response raises ArcmiraReadError with status, body and selected response headers; the error message retains the refusal body and redacts echoes of the supplied key. Visual editor presentation of these exceptions remains unverified.
Validation status
The candidate targets mature LFX 1.12.3 (September 22, 2026). Local HTTP fixtures use real HTTPX transport and prohibit socket connections; no real API key or paid call is involved. Released LFX manifest/AST validation and package build are recorded separately from full component import, native tool execution and frontend testing. The isolated LFX 1.12.3 runtime passes extension import validation, installed-extension discovery, four native component/tool checks and eleven HTTP fixture tests. Native tool output preserves the complete response as an artifact. Visual editor presentation and live-account reads remain unverified.
uv sync --frozen
uv run --frozen python -m unittest discover -s tests -v
uv run --frozen lfx extension validate . --execute-imports
uv run --frozen lfx extension list --format json
uv build
The upstream integration proposal is Langflow issue 15539. An open proposal is not a catalog listing or maintainer approval.
Metadata
Release files for lfx-arcmira 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| lfx_arcmira-0.1.0.tar.gz | 8.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lfx_arcmira-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.8 kB
Release files / lfx_arcmira-0.1.0.tar.gz
| Download URL | lfx_arcmira-0.1.0.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2395f440cef5d67a37b5c7ad8651070883150b937031608314baf2c881de5df
|
|
BLAKE2b-256 checksum How to use checksums |
2af3e90ab15ea7f46cb489a4840e0083597f4fbbbf2aa7a360b3a010b672fb0b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency logRelease files / lfx_arcmira-0.1.0-py3-none-any.whl
| Download URL | lfx_arcmira-0.1.0-py3-none-any.whl |
|---|---|
| Size | 11.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cc9f184306220fed035a96bf554fcc3b5495dc15da6b931c0214d64201aba7a5
|
|
BLAKE2b-256 checksum How to use checksums |
9fa7230b9924058f1c1ddf87f182c8b093df10ac4c8f349938925ea232441bd7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 11, 2026.
Transparency log