Alguns produtos e recursos estão sendo renomeados. Os recursos de playbook generativo e de fluxo também estão sendo migrados para um único console consolidado. Confira os detalhes.
Ao fazer chamadas para a API, sua solicitação especifica o projeto do agente.
Esse projeto é conhecido como o projeto do recurso.
Por exemplo,
na solicitação REST curl abaixo,
o projeto associado a AGENT_ID é o projeto de recurso,
e o projeto associado à conta de serviço usada para gerar TOKEN
é o projeto do consumidor:
curl -X GET
-H "Authorization: Bearer TOKEN"
"https://REGION_ID-dialogflow.googleapis.com/v3/projects/PROJECT_ID/locations/REGION_ID/agents/AGENT_ID"
Um projeto pode ter o papel de consumidor e de projeto de recurso.
Os dados, as cobranças e as cotas do agente são associados apenas a este projeto.
Quando os projetos de consumidor e de recurso são diferentes, as cobranças, as restrições de cota, as informações do agente e um requisito para ativar a API são aplicáveis a um ou a ambos os projetos, conforme descrito na tabela a seguir.
Descrição
Projeto do consumidor (projeto de conta de serviço)
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-18 UTC."],[[["\u003cp\u003eMultiple Google Cloud projects can be used with Dialogflow, potentially separating authentication, quotas, and billing from agent data.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003cem\u003econsumer project\u003c/em\u003e is the project owning the service account used for API calls, whereas the \u003cem\u003eresource project\u003c/em\u003e is the project containing the agent's data.\u003c/p\u003e\n"],["\u003cp\u003eA single project can serve as both the consumer and resource project, in which case all data, charges, and quotas are associated with that one project.\u003c/p\u003e\n"],["\u003cp\u003eThe consumer project is charged and subject to quotas, while the resource project stores the agent data.\u003c/p\u003e\n"],["\u003cp\u003eThe Dialogflow API must be enabled for both the consumer project and resource project when they are different.\u003c/p\u003e\n"]]],[],null,["# Using multiple projects\n\nIn some cases, you might need to create multiple Google Cloud projects to use\nDialogflow:\n\n- You might find it useful to create one project for authentication, quotas, and billing, and additional projects for [agent](/dialogflow/es/docs/agents-overview) data.\n\nConsumer and resource projects\n------------------------------\n\nWhen you make calls to the API, you typically provide\n\n[service account keys for authentication](/dialogflow/cx/docs/quick/setup#auth).\n\nEach service account is owned by a specific project,\nbut service accounts might be\n\n[provided roles to access resources for other projects](/dialogflow/cx/docs/concept/access-control#gcp-console)\n\nThe project associated with the service account you provide for an API call\nis referred to as the *consumer project*.\n\nWhen you make calls to the API, your request specifies the agent's project.\nThis project is referred to as the *resource project*.\n\nFor example,\nin the following REST curl request,\nthe project associated with `AGENT_ID` is the resource project,\nand the project associated with the service account used to generate `TOKEN`\nis the consumer project: \n\n```\ncurl -X GET\n -H \"Authorization: Bearer TOKEN\"\n \"https://REGION_ID-dialogflow.googleapis.com/v3/projects/PROJECT_ID/locations/REGION_ID/agents/AGENT_ID\"\n```\n\nOne project can play the role of both consumer and resource project.\nAgent data, charges, and quotas are associated only with this project.\n\nWhen consumer and resource projects are two different projects, charges, quota\nconstraints, agent information, and a requirement to enable the API are\napplicable to either or both projects, as described in the following table."]]
